ci-cd-and-automation

Create a workflow file at .github/workflows/ci.yml that triggers on pull requests and pushes to main. Add jobs that install dependencies with npm ci, then run lint, tsc --noEmit, tests with coverage, build, and npm audit as sequential gates.

Use the services key to spin up a PostgreSQL container with health checks, then run migrations and integration tests against it. Store the database password in GitHub Secrets rather than hardcoding credentials in the workflow file.

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 until all checks pass.

Slow pipelines usually lack dependency caching and run jobs sequentially. Apply npm caching via setup-node, 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 releasing them. Flags let you canary releases to a percentage of users and roll back by disabling the flag, but they should be removed after full rollout to avoid technical debt.

Yes. Copy the specific failure output from the CI run and give it to the agent with instructions to fix and verify locally before pushing. Lint failures map to auto-fix commands, type errors to targeted fixes, and test failures to a debugging workflow.