< Abusing Git Trailers for Faster CI/CD

In Don't Run It Twice, I wrote about why our CI skips the checks an agent has already run. This is more on the how: using git trailers.

A trailer is a Key: value line at the bottom of a commit message, under a blank line[1]. You may have seen them as Signed-off-by and Co-authored-by[2] against your commit.

$ git commit -m "Fix the stale cache" --trailer "Checks-Run: tsc, lint, unit"
$ git log -1 --format='%(trailers:key=Checks-Run,valueonly)'
tsc, lint, unit

We have a hook that has coding agents run tsc, lint and the unit tests before they push. In the vast majority of cases this is running on a cloud VM somewhere.

CI used to repeat this on every push. And since we care about CI/CD times this was an aggressive fan-out to keep cycle times short.

My solution: the agent's commit records what it ran as a trailer, like the Checks-Run line above. The build on a PR/branch reads the trailer off the commit and skips the steps it lists. Everything else runs as normal.

The trailer travels with the commit, so CI has it the moment it has the code. There's no cache to stand up and no service to call.

Like a PR description, a trailer is a claim, not a proof. So only the PR build accepts the trailers. main runs every step again, whatever the trailer says.

The trailer took about three minutes off each PR build[3]. The wall-clock time was the obvious win, but the bigger one was contention. Fewer Buildkite agents (the build-runner kind of agent) get spun up, fewer jobs sit waiting for one, and the ones that stay warm cache better. It's queuing theory at work: waits grow non-linearly as a pool gets busier, so shedding a little load cuts a lot of waiting. At 100+ PRs a day that is a lot of build minutes.

Yes, it's a poor man's Bazel[4]. If your agents already run the checks before they push, give it a shot.

Also read: Don't Run It Twice, The Cold Read, and Never Pick It Up Twice.

Discuss and share via the meta page . Filed under AI, Code, and 100PR.

Footnotes

  1. The plumbing is git interpret-trailers, and git commit --trailer and the %(trailers) placeholder in git log use the same parsing. Keys are limited to letters, numbers and hyphens. ↩

  2. GitHub reads Co-authored-by to credit a second author on a commit. ↩

  3. Builds were 10+ minutes overall, but now ~1.5 minutes. ↩

  4. Bazel hashes each step and looks the hash up in a shared cache. Mine goes on what a hook saw the agent run. ↩