Two thousand pull requests in 151 days

PR #2000 merged thirteen seconds after it opened. That's not efficiency, that's what happens when the reviewer is also the writer and the tests already passed. 151 days, 2,000 pull requests, one person plus a lot of AI doing the grunt work. The honest footnote: a merged PR is a claim that something works, not proof. Some of those 2,000 were fixes for the 1,999 before them.

PR #2000 merged thirteen seconds after it opened. When you're the writer and the reviewer, review is fast and also suspect. 2,000 PRs in 151 days, and a fair number were cleaning up the mess left by earlier ones.

PR #2000 merged thirteen seconds after it opened on a Friday evening. Thirteen seconds because the writer and the reviewer are the same person, backed by a lot of AI. 2,000 pull requests in 151 days sounds heroic until you notice how many of them were fixing the ones that came before.

PR #2000 merged thirteen seconds after it opened. Fast, because the person opening it and the person approving it are the same, with AI doing most of the typing. 2,000 pull requests in 151 days. The number I keep coming back to isn't the total, it's the share of PRs that existed only to undo an earlier one. A merged PR is a claim that something works, not a guarantee.

PR #2000 merged thirteen seconds after it opened. That's the speed you get when the writer and reviewer are the same person. 2,000 PRs in 151 days, plenty of them cleaning up the ones before.

Pull request #2000 merged thirteen seconds after it opened. That pace only works because most of the repo is building itself. https://www.jakelawrence.xyz/blog/two-thousand-pull-requests