What problem does it solve?
Forge CI scaffolding solves the problem of setting up consistent, secure GitHub Actions pipelines without manual drift, fragile edits, or forgetting essential checks across linting, testing, builds, and security scanning.
Core Features & Use Cases
- Tier-1 codegen with guardrails: Generates banner-protected Tier-1 workflows (so they’re reproducible and regenerated by
forge generate) while preventing accidental hand edits from silently diverging from the declared config.
- Clear extension paths for customization: Lets you extend CI either by using
ci.extra_jobs to append jobs into the generated ci.yml, or by adding Tier-2 workflows that forge never overwrites.
- Local verification helpers: Documents
forge ci verify-generated and other helper subcommands so teams can run the same gates locally (e.g., drift detection, KCL validation, vuln scan, and migration safety).
Use case example: You want every PR to automatically run Go + frontend lint, unit tests with race mode, build artifacts (including multi-arch images when configured), vulnerability scanning, and (optionally) E2E—while still adding a team-specific docs job without forking or editing generated CI YAML by hand.
Quick Start
Run forge ci verify-generated to confirm the checked-in workflows match what forge would generate from your current forge.yaml.