Contribute a gate recipe
We are collecting quality-gate recipes: CI configs you can copy that stop a bad change from merging, one per stack. Send us one that works on your projects, and we will publish it with your name and a link to you.
What a recipe is
A recipe is the gate for one stack, such as Next.js, Django, FastAPI, Go, Rails, Spring, .NET or Rust. It:
- runs the project's tests and fails on a failing test,
- sets a coverage floor,
- generates an SBOM (CycloneDX) for the build,
- checks dependency licenses against a policy,
- scans the change for committed secrets.
Write it as a plain CI workflow (GitHub Actions, GitLab CI, Forgejo Actions or similar), so it works for people who don't use AI CodeOps. If you do use AI CodeOps, add the release check call too: your CI asks POST /api/release/check whether a pull request may merge, with options such as minCoveragePct, disallowedLicenses and requiredWorkflows. See quality gates and the API reference.
What makes a good one
- It runs. You have used it on a real repository, and you tell us which tool versions.
- Each step says what it checks and why, in a comment or a short README.
- No secrets, tokens or internal hostnames in it.
- It fails closed: if a check can't run, the gate says so instead of passing.
New to gates? Start with the quality gates guide, coverage gates and fail-open vs fail-closed.
Credit
Each published recipe names its author, with a link to the site or profile you choose.
How to send one
The open recipes repository is coming soon; its link will be here when it is public. Until then, email your recipe to [email protected] with "Gate recipe" in the subject: the config, the stack and versions it was tested on, and the name and link to credit.
Looking for something to start from? Our templates include gated workflows for Python and Next.js projects.