ci-cd-and-automation

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

Use GitHub Actions service containers to run Postgres alongside your job, then apply migrations with prisma migrate deploy before running integration tests. Store database credentials in GitHub Secrets rather than hardcoding them in the workflow.

Run lint, type checking, unit tests, build, integration tests, security audit, and bundle size checks in sequence. Configure branch protection so all status checks pass and at least one approval exists before merge is allowed.

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

Use feature flags when you want to merge incomplete or risky features to main without enabling them for users. Flags support canary rollouts and instant rollback without redeploying, but set a cleanup date so stale flags do not become technical debt.