The protection I switched off to make CI pass
I sent the bouncer home so a Go test could get in. It turned out he'd been turning away malware since the summer, and he wouldn't come back.

I sent the bouncer home so a Go test could get in. It turned out he'd been turning away malware since the summer, and he wouldn't come back.

A release token showed up in use from four machines in AWS that I couldn't account for. Two hours later it turned out to be my own runner fleet, and I'd fixed the real problem anyway.

A plugin marketplace has no registry, so whatever's on main is what people install. I tried twice to get CI to keep the version honest before settling for a check that makes me type a command.

Twenty agent sessions, one GitLab account on the Free plan and a rate limit that kept tripping. The swarm was the obvious suspect, right up until I traced it.

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.

A spec, a how-to and a README walk into a repo. Only one of them should still be there in six months.

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.

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?

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.

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.
