Every suppression is a claim
Forty-two comments telling a checker to stand down. I went through them one at a time to see what each was actually asserting, and some of them were wrong.
Tags
28 pages
CI/CD
Which tests would you cut when the bill arrives?
The runner fleet cost $270 I didn't have, so it went off. The tests stayed on, and the savings came from everything I'd been paying for twice.
The runner fleet that scales to zero
The homelab finally ran out. Not disk this time, capacity. So the overflow went to AWS, on the condition that it costs nothing when nobody's pushing.
The repo that downloaded 170 gigabytes
An hour to compile and 170GB of artefacts to clean up afterwards. Rust has a built-in answer to that, and I only used half of it.
Nine tags that were never on the branch
colophon works out the version your commits have earned, opens the release as a merge request, and tags what actually landed. Not what your forge says did.
One cache key per lockfile filled my runner's disk
The documented cargo cache key gives every lockfile its own cache. On a self-hosted runner that fills the disk. Whose disk was the advice for?
Your first run with skillup
A change that ships without a version bump reaches nobody, and nothing tells you. Ten minutes in a throwaway directory to see it happen, and then catch it.
Ready for human
I run a coding session per repository and they can't talk to each other. For a while the thing carrying messages between them was me, and I kept getting it wrong.
The fastest job is the one you never run
Half my CI jobs ran for no reason on every merge request. Skipping them with rules:changes, and why that is trickier than the manual suggests.
The marketplace I had to defend from my own attack surface
Opening a public marketplace for agent workflows meant publishing an attack surface, and then having to defend it from my own convenience.
