ci-cd-and-automation

Create a workflow file at .github/workflows/ci.yml that triggers on pull requests and pushes to main. Add sequential steps for npm ci, lint, tsc --noEmit, tests with coverage, build, and npm audit so every change passes all quality gates before merge.

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

Feature flags decouple deployment from release by toggling features at runtime, enabling canary releases and instant rollback without redeploying. Staged rollouts promote builds through staging to production with verification and monitoring 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 test suites across runners.

No, CI should never hold production secrets. Use separate credentials for CI test environments stored in GitHub Secrets, and keep production secrets in the deployment platform or a vault.