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, using actions/setup-node with dependency caching.

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 includes lint, type checking, unit tests, build, integration tests, optional E2E tests, security audit, and bundle size checks. No gate should be skipped, and branch protection should block merges until all checks pass.

Slow pipelines usually lack dependency caching and run jobs sequentially. Apply setup-node caching, split lint, typecheck, and test 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 releasing them. Flags enable canary rollouts, A/B tests, and instant rollback without redeploying, but should be removed after full rollout to avoid technical debt.

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