Fetching from the wire…
01
02
03
04
05
06
07
08
Top 5 · 2026-04-05 · source-backed
Fourteen times more commits. Not 14% more. 14x.
GitHub COO Kyle Daigle dropped this number in a conversation covered by Simon Willison: the platform is currently running at 275 million commits per week, which annualizes to roughly 14 billion for 2026. In all of 2025, GitHub saw 1 billion total. GitHub Actions usage tells the same story from a different angle. It quadrupled from 500M minutes/week in 2023 to 2.1 billion minutes this week.
There's only one explanation for commit volume growing 14x in a year. Machines are writing code. A lot of it.
I've been watching my own commit patterns change since I started using Claude Code daily, and my output roughly tripled. But 14x across the entire platform means something different is happening at scale. Companies aren't just using AI to write code faster. They're running agents that generate commits autonomously. The Anthropic 2026 Agentic Coding Trends Report backs this up: 78% of Claude Code sessions now involve multi-file edits, up from 34% a year ago. Average session length went from 4 minutes to 23 minutes.
Here's what worries me. Code review doesn't scale 14x. Testing doesn't scale 14x. The 12,000 AI-generated blog posts that OneUptime committed in a single push this week (143-point HN discussion about content quality) is the writing equivalent of what's happening to code. Volume goes vertical. Quality control stays flat.
If you're running a team, the question isn't whether AI is generating code in your org. It is. The question is whether your review and testing infrastructure can handle the throughput. Every CI/CD pipeline, every code review process, every security scan was designed for human-speed commit rates. We're now operating at machine speed.
What to do: audit your CI/CD pipeline capacity against actual commit volume trends. If your Actions minutes are climbing faster than your test coverage, you've got a gap that's going to bite you.
Each link below shares sources, entities, or timing with this story.
Simon Willison uses Claude Code / Shared entities / Same source domain / Shared topic / What happened next / Tension
Linked by a graph relationship (Simon Willison uses Claude Code); both cover Claude Code, GitHub, Simon Willison; reported by the same outlet (simonwillison.net).
Simon Willison uses Claude / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Simon Willison uses Claude); both cover Actions, GitHub, GitHub Actions, Simon Willison; reported by the same outlet (simonwillison.net).
Simon Willison uses Claude Code / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Simon Willison uses Claude Code); both cover Claude Code, GitHub, Simon Willison; reported by the same outlet (simonwillison.net).
Linked by a graph relationship (Simon Willison uses Claude Code); both cover Average, Claude Code, GitHub; reported by the same outlet (github.com).
Simon Willison uses Claude Code / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Simon Willison uses Claude Code); both cover Actions, Claude Code, GitHub; overlapping topics (action, claude, code, different, review).
Simon Willison uses Fable / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Simon Willison uses Fable); both cover Claude Code, GitHub Actions, Simon Willison; reported by the same outlet (simonwillison.net).
Simon Willison uses Claude Code / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Simon Willison uses Claude Code); both cover Claude Code, Code, GitHub; reported by the same outlet (github.com).
Linked by a graph relationship (Simon Willison uses Claude Code); both cover Claude Code, GitHub, Simon Willison; reported by the same outlet (simonwillison.net).