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 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 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, even for CI-only databases.

A complete pipeline runs lint, type checking, unit tests, build, integration tests, optional E2E tests, security audit, and bundle size checks. No gate should be skipped; failures must block merging through branch protection rules.

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 with matrix builds.

Use feature flags to merge incomplete or risky features to main without enabling them, allowing canary rollouts and instant rollback by disabling the flag. Set a cleanup date when creating flags, since permanent flags become technical debt.