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 dependency install, lint, type check, tests, build, and security audit using actions/checkout and actions/setup-node.

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

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 skippable, and failures must block merging via branch protection.

Slow pipelines usually lack dependency caching and run jobs sequentially. Fix this by enabling the setup-node cache option, splitting lint, typecheck, and test into parallel jobs, using path filters, and sharding 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 let you canary releases, run A/B tests, and roll back by disabling the flag instead of reverting code.