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, and build in sequence or as parallel jobs.

Define a Postgres service container in the workflow job with health checks, then run migrations and integration tests against it. Store the database password in GitHub Secrets rather than hardcoding credentials, even for CI-only test databases.

A complete pipeline runs lint, type checking, unit tests, build, integration tests, optional E2E tests, security audit via npm audit, and bundle size checks. Every gate must pass before merge, and failures should be fixed rather than skipped or disabled.

Slow pipelines usually lack dependency caching and run jobs sequentially. Enable the cache option in setup-node, split lint, typecheck, and test into parallel jobs, use path filters to skip irrelevant jobs, and shard large test suites across runners.

Feature flags decouple deployment from release by wrapping unfinished code in a conditional check like featureFlags.isEnabled. This allows merging to main early, rolling out gradually to user percentages, and disabling features without reverting code.

CI failures should always block merging through branch protection rules requiring status checks to pass. Ignoring or silencing failures lets broken states accumulate, and flaky tests should be fixed rather than retried or skipped.