ci-cd-and-automation

Create a workflow file at .github/workflows/ci.yml that triggers on pull requests and pushes to main. Add steps for checkout, Node.js setup with npm caching, dependency installation via npm ci, then run lint, type check, tests, and build in sequence.

Use GitHub Actions service containers to run PostgreSQL alongside your job, with health checks to ensure readiness. Store credentials in GitHub Secrets, run migrations with prisma migrate deploy, then execute integration tests against the service URL.

A complete pipeline includes lint, type checking, unit tests, build, integration tests, optional E2E tests, security audit via npm audit, and bundle size checks. No gate should be skippable, and failures must block merging through branch protection.

Slow pipelines usually lack dependency caching and run jobs sequentially. Enable the setup-node npm cache, 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 for users. Flags support canary rollouts, A/B tests, and instant rollback without redeploying, but should be removed after full rollout to avoid technical debt.