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