CI recipes
NAME
ci - five pipeline recipes, each on its own page
The tool is one command with an exit code, so wiring it into a pipeline is mostly a matter of where the input comes from and how the exit status is read. These five recipes cover the arrangements that come up; pick the one whose runner you already have.
WHAT TO CHECK WHERE
| Job | Input | Runs on | Threshold |
|---|---|---|---|
| pull request | a committed fixture | every push | any |
| local commit | a committed fixture | the git hook | any |
| nightly | yesterday’s dump | a schedule | breaking |
| pre-release | full dump, sample 0 | a tag | breaking |
The distinction that drives the threshold column: a reviewed fixture can afford --fail-on any because a new field there was a deliberate edit, whereas unreviewed production data arrives noisy and a job that trips on every optional field gets muted within a fortnight.
RECIPES
A hosted workflow that fetches the verified binary and annotates the lock file inline on a pull request.
A job built on the published image, with the one pipefail trap that otherwise passes every drift green.
A scheduled shell runner over yesterday’s full dump, separating a vanished input from a real break.
A local git hook over a committed fixture, strict, so a shape change and its lock land in one commit.
Running the immutable image directly, with the entrypoint and tag rules that keep a check honest.
Across all five: pin the version in one place, verify the download, keep the lock in version control, and never silence a finding by adding an ignore entry in the same breath.