What problem does it solve?
It enforces reliable CI/CD pipelines so pull requests are validated, builds are reproducible, tests run in the correct order, secrets are protected, and deployments are reversible.
Core Features & Use Cases
- Quality Gates: Enforces ordered gates (lint → type-check → unit tests → build → integration → E2E → security audit → bundle size) and recommends running the first gates in parallel.
- GitHub Actions Best Practices: Provides job splitting, pinned actions, dependency caching, artifact caching, concurrency controls, and Playwright setup for E2E.
- Integration & E2E Testing: Shows how to run integration tests with service containers (Postgres) and E2E with Playwright including failure artifact uploads.
- Monorepo & Path Filtering: Uses path filters or dorny/paths-filter to run only affected jobs in monorepos.
- Deployment & Rollback Strategies: Recommends rolling/canary/blue-green strategies, staged rollouts with verification thresholds, and a dedicated rollback workflow.
- Security & Environment Management: Stresses GitHub Secrets, environment separation, and branch protection rules to block merges on failing checks.
Quick Start
Set up the GitHub Actions workflow with parallel lint/typecheck/test jobs, a dependent build job, conditional integration and E2E jobs, dependency and artifact caching, secure secrets via GitHub Secrets, and a rollback workflow.