ci-cd-and-automation

Create a workflow file at .github/workflows/ci.yml that triggers on pull requests and pushes to main. Define jobs that install dependencies with npm ci, then run lint, tsc --noEmit, tests with coverage, build, and npm audit in sequence.

Use GitHub Actions services to spin up a PostgreSQL 16 container with health checks alongside your job. Run migrations with prisma migrate deploy, then execute integration tests against the service using credentials stored in GitHub Secrets.

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; failures must block merge through branch protection rules.

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

Use feature flags when you want to merge incomplete or risky features to main without enabling them for users. Flags allow canary rollouts, A/B tests, and instant rollback by disabling the flag, but should be removed after full rollout.

No, CI should never hold production secrets. Store CI credentials in GitHub Secrets or a vault, keep production secrets in the deployment platform, and commit only .env.example templates and non-sensitive test environment files.