GitHub adds Pull Request rate limits — first time the platform throttles «contributions welcome»
TL;DR
GitHub now lets repos cap how many open PRs a non-write-access contributor can have. PR throughput rose 3.6× in four years — AI-generated PRs are the main driver.
GitHub announced Pull Request Limits on June 18 — repository maintainers can now cap the number of simultaneously open PRs from users without write access. First time in GitHub's history that the platform-default «contributions welcome» posture has been flipped to «get in line».
Mechanics: once the cap is hit, a contributor must close or merge an existing PR before opening a new one. Draft PRs don't count; PRs opened by Copilot or other AI agents do. Maintainers can add trusted contributors to a bypass list (no write privileges granted). Configuration lives under Moderation Options → Interaction Limits.
The numbers explain why. PRs merged on GitHub per month: January 2023 ≈ 25M. June 2026: 90M+. 3.6× in four years. Most of the growth isn't new developers — it's AI-generated PRs. heise calls it «GitHub's unstated AI-slop governance». The Register reported in February that GitHub was researching a «PR kill switch».
Maintainer feedback is blunt. AutoGPT's Nicholas Tindle on GitHub's blog: «This makes me want to review PRs again.» Homebrew's Mike McQuaid: «We can still take external contributions — at a pace maintainers can actually process.» Both projects are among the worst-hit by AI PR floods.
Next: PR archive ships soon. Issue limits in development. The bypass list will eventually plug into account history and org membership for «smart allow-list».
The default rule of open-source collaboration for 17 years — «more PRs is better, all welcome» — got an official pause this year, the year AI pushed the marginal cost of a PR to zero.
via GitHub Blog / InfoWorld
Mechanics: once the cap is hit, a contributor must close or merge an existing PR before opening a new one. Draft PRs don't count; PRs opened by Copilot or other AI agents do. Maintainers can add trusted contributors to a bypass list (no write privileges granted). Configuration lives under Moderation Options → Interaction Limits.
The numbers explain why. PRs merged on GitHub per month: January 2023 ≈ 25M. June 2026: 90M+. 3.6× in four years. Most of the growth isn't new developers — it's AI-generated PRs. heise calls it «GitHub's unstated AI-slop governance». The Register reported in February that GitHub was researching a «PR kill switch».
Maintainer feedback is blunt. AutoGPT's Nicholas Tindle on GitHub's blog: «This makes me want to review PRs again.» Homebrew's Mike McQuaid: «We can still take external contributions — at a pace maintainers can actually process.» Both projects are among the worst-hit by AI PR floods.
Next: PR archive ships soon. Issue limits in development. The bypass list will eventually plug into account history and org membership for «smart allow-list».
The default rule of open-source collaboration for 17 years — «more PRs is better, all welcome» — got an official pause this year, the year AI pushed the marginal cost of a PR to zero.
via GitHub Blog / InfoWorld
