GitHub Octoverse 2026
- ID
- 40420
- Status
- summarized
- Published
- 29 Oct 2026, 12:45 AM
- Fetched
- 29 Oct 2026, 1:00 AM
- Provider
- Simon Willison
- Category
- developer-ai
- Original URL
- https://simonwillison.net/2026/Oct/28/github-octoverse-2026/
- Source URL
- https://simonwillison.net/atom/everything/
Summary
- Score
- 6.5
- Created
- 29 Oct 2026, 1:01 AM
- Tags
- Audience
- developersvibe_codersai_agent_userssaas_founders
What happened
Simon Willison live-blogged GitHub's Octoverse 2026 announcement from GitHub Universe, where EVP Jay Parikh reported merged pull requests tripled in under a year to 220 million per month, commits more than tripled to 7.38 billion per month (most of the growth in the second half of 2026), and the new-repository rate doubled to 30.3 million per month. The report also adds industry breakdowns via a fine-tuned multilingual embedding model mapped to NAICS sectors, plus a count of repos mentioning interoperability or reverse engineering (clean-room implementations, drop-in replacements, protocol re-implementations). Methodology notes say country rankings were adjusted by extracting ISO codes from profiles with LLM classification to offset VPN bias.
Why it matters
The 3x jump in merged PRs (220M/month) with commit growth concentrated in H2 2026 means the scarce resource is shifting from writing code to reviewing and merging it — if your team tracks anywhere near that curve, your review queue, CI minutes, and branch-protection rules are the constraint, not code generation. Note the report is GitHub's own platform aggregate with no per-repo or Malaysia-specific breakdown, so it is context for capacity planning, not a benchmark you can quote for your own repo.
Discussion angle
If merged PR volume tripled while team headcount didn't, which breaks first in your workflow — reviewer attention, CI spend, or trust in what's being merged — and what would you change about review policy if you suspected a chunk of those PRs were agent-generated?