Time chart of our observed incident with three lanes: the default branch, an earlier change, and a dependent pull request based on it. First the earlier change merges, then its branch ends, then the dependent pull request closes. Its commit marks are still drawn. Closing the pull request does not by itself show that Git erased its commits.

Landing one pull request closed the next

I like small pull requests because I can follow what changed without having to keep the whole project in my head. They’re easier to review and easier to revert. When an agent is doing the implementation, a small change also gives me a more manageable piece of work to check before it goes onto the default branch. Some changes depend on work that hasn’t merged yet. I can still review them separately by stacking their pull requests, with each branch based on the one before it. That introduces a responsibility for the tool that lands them: merging one change shouldn’t interrupt review of the change that comes next. ...

November 17, 2026 · Dave Voyles
Locked steel hatch in a dark factory floor — the landing gate that will not lift without a stamp

The last click is still yours

Companion to GitHub tokens for agent fleets and the agent production system series. Words I use below Agent — a program that writes and lands code for you, in a chat session Pull request (PR) — a proposed change waiting for review; on GitHub it has its own page, with a button to accept it Merge — accepting that proposed change so it becomes part of the main project GitHub App — a robot you install on a GitHub project so it can click buttons as itself — not as you; it can approve, and it can merge; people treat this robot as the “real” setup, and it is not — it is extra (this post does not tell you how to install one; if you later want that robot, read the token post) Lock — a program that says no when a rule is broken; the agent cannot talk it into a yes; I also call this the landing floor Stamp — a review that applies to one exact version of the code; “looks good” in chat is not a stamp Automatic tests — checks that run by themselves when you propose a change; green means they passed Those seven words are the whole toolkit. Now the point. ...

August 21, 2026 · Dave Voyles
A long-lived access key left exposed on an open laptop in a dark ops room

Don't paste your GitHub key in chat

Companion to The last click is still yours and the agent production system series. Words I use below Agent — a program that writes code for you in a chat session Pull request (PR) — a proposed change waiting for review; on GitHub it has its own page, with a button to accept it Merge — accepting that proposed change so it becomes part of the main project Personal login — you, signed in as yourself; when you type commands, GitHub sees your name GitHub App — a robot you install on a GitHub project so it can click buttons as itself — not as you; it can approve, and it can merge Short-lived token — a temporary key the robot gets to prove it may click; it dies in about an hour, and after that it is junk PAT (personal access token) — a long-lived key tied to you; if it leaks into a chat log, it keeps working until someone turns it off Broker — a small program that hands out a short-lived token when the rules say yes; the agent asks, the broker decides, and the agent does not invent a key Automatic tests — programs that run by themselves when you propose a change; green means they passed Those nine words are the toolkit. Now the point. ...

August 18, 2026 · Dave Voyles