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 failures block the merge.

Define a postgres service container in the job with health checks using pg_isready, then run migrations and tests against localhost:5432. Store the CI database password in GitHub Secrets rather than hardcoding credentials.

A complete pipeline includes lint, type checking, unit tests, build, integration tests, optional E2E tests, security audit, and bundle size checks. No gate should be skipped; fix the underlying issue instead of disabling rules or tests.

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

Use feature flags when you want to merge incomplete or risky features to main without releasing them. Flags enable canary rollouts, instant rollback without redeploying, and A/B testing, but should be removed after full rollout to avoid technical debt.