ci-cd-and-automation

Create a workflow triggered on pull requests and pushes to main that runs npm ci, lint, tsc --noEmit, tests with coverage, build, and npm audit. Use actions/setup-node with the cache option to speed up dependency installation.

Define a postgres service container in the job with health checks, then run migrations and tests against it using a DATABASE_URL pointing at localhost:5432. Store the CI database password in GitHub Secrets rather than hardcoding it.

A complete pipeline runs lint, type checking, unit tests, build, integration tests, optional E2E tests, a security audit, and a bundle size check. No gate should be skipped — fix the underlying issue instead of disabling rules or tests.

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

Yes, add a deploy-preview job conditioned on pull_request events that builds the branch and deploys it with a platform CLI such as Vercel using a token stored in GitHub Secrets. Every PR then gets an isolated environment for manual testing.

Use feature flags to merge incomplete or risky features to main without enabling them, allowing canary rollouts and instant rollback by toggling the flag. Set a cleanup date when creating each flag so stale flags do not become technical debt.