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 with coverage, build, and npm audit, using actions/setup-node with dependency caching.

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

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, and failures must block merging through branch protection rules.

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

Feature flags decouple deployment from release by gating new code behind runtime checks. Deploy code to production with the flag disabled, then enable it gradually for canary rollouts, and remove the flag and dead code after full rollout.

Never skip CI, even for trivial changes, since small edits still break builds. If the pipeline feels too slow, optimize it with caching and parallelism instead of bypassing gates or disabling failing tests.