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 npm ci, lint, tsc --noEmit, tests with coverage, build, and npm audit so every change passes all quality gates before merge.

Define a postgres service container in the job with health checks, expose port 5432, and store credentials in GitHub Secrets. Run prisma migrate deploy against the service, then execute integration tests with the DATABASE_URL pointing at localhost.

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 skippable, and branch protection should block merges when any gate fails.

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 large test suites across runners.

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 by disabling the flag, but each flag needs a cleanup date to avoid permanent technical debt.

Fix the flakiness rather than re-running or disabling the test, since flaky tests mask real bugs and erode trust in the pipeline. Investigate timing dependencies, shared state, and external service calls, then stabilize or isolate the test.