ci-cd-and-automation

Create a workflow file at .github/workflows/ci.yml that triggers on pull requests and pushes to main. Configure jobs for lint, type check with tsc --noEmit, tests, build, and npm audit, using actions/setup-node with npm caching.

Define a postgres service container in the job with health checks, then run migrations and tests against it using a DATABASE_URL environment variable. Store credentials in GitHub Secrets rather than hardcoding them in the workflow file.

Feature flags decouple deployment from release by toggling features in code at runtime, enabling canary releases and instant rollback without redeploying. Staged rollouts promote builds through staging to production environments with verification between stages.

Slow pipelines usually lack dependency caching and run jobs sequentially. Apply npm caching via setup-node, split lint, typecheck, and test into parallel jobs, use path filters to skip unrelated work, and shard large test suites across runners.

No, CI should never hold production secrets. Use separate credentials for CI testing stored in GitHub Secrets, keep production secrets in the deployment platform or a vault, and commit only .env.example templates to the repository.