ci-cd-and-automation

Create a workflow file at .github/workflows/ci.yml that triggers on pull requests and pushes to main. Add jobs for lint, type checking with tsc --noEmit, tests, build, and npm audit, using actions/setup-node with dependency caching.

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

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 merge through branch protection rules.

Slow pipelines usually lack caching and run jobs sequentially. Cache node_modules with setup-node, split lint, typecheck, and test into parallel jobs, use path filters to skip unrelated work, and shard test suites with matrix builds.

No, CI should never hold production secrets. Use separate secrets for CI testing stored in GitHub Secrets, keep production credentials in the deployment platform or a vault, and commit only .env.example templates.

Use feature flags to merge incomplete features to main without enabling them, decoupling deployment from release. Flags support canary rollouts and instant rollback, but set a cleanup date since permanent flags become technical debt.