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, then run migrations and integration tests against it using a DATABASE_URL environment variable. Store credentials in GitHub Secrets rather than hardcoding them, even for CI-only databases.

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 dependency caching and run jobs sequentially. Apply caching via setup-node, split lint, typecheck, test, and build 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 support canary rollouts and instant rollback without redeploying, but each flag needs a cleanup date to avoid 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 as common root causes.