GitHub Limits PR Noise

GitHub is introducing pull request limits to combat the deluge of contributions overwhelming open-source maintainers. With the number of merged pull requests skyrocketing to over 90 million monthly, distinguishing valuable contributions from low-quality noise has become a significant challenge.

The new feature restricts the number of open pull requests a user without write access can maintain simultaneously. Exceeding this limit requires closing or merging an existing request before a new one can be opened. This persistent, configurable control offers maintainers much-needed agency in managing their project's workflow.

This move is a direct response to developer feedback about managing overwhelming contribution volumes, exacerbated by the rise of AI code generation. Draft pull requests and contributions from AI agents like GitHub Copilot CLI count towards the limit, encouraging more thoughtful submissions.

Trusted contributors can be added to a bypass list, exempting them from these limits. This mechanism aims to balance quality control with maintaining open contributions.

The Cost of Noise

The sheer volume of pull requests has made reviewing them a daunting task. In January 2023, developers merged approximately 25 million pull requests monthly; that figure has since surged to over 90 million. This exponential growth, partly fueled by AI tools, strains the capacity of volunteer maintainers.

This feature is great. We’ve had problems on Homebrew for a while with enthusiastic users submitting many pull requests that need near identical review. AI further accelerated it. This allows us to still have outside contribution and maintainers contribute more while gating users to a level of pull requests we can cope with.

Nicholas Tindle, AutoGPT, and Mike McQuaid, Homebrew, have voiced support, noting how the limits help manage contributor volume without stifling participation. OpenClaw also highlighted the necessity of such tools, having previously built custom bots to combat spam.

What's Next

GitHub plans to expand these controls, with several features on the roadmap:

• Archiving pull requests (shipping soon): Allows admins to hide low-quality or spammy requests from the main view without permanent deletion.
• Issue limits (in development): Similar caps will be applied to issues, restricting the number a user can have open.
• Smarter bypass signals (up next): Automated exemption based on signals like account age or prior merged contributions, reducing manual curation.
• Cross-repository controls (exploring): Mechanisms to address users submitting pull requests across numerous repositories simultaneously.

These enhancements aim to provide more granular control over contribution flow, acknowledging the evolving landscape of collaborative development and the increasing role of AI agents in the software development lifecycle.

Thank you Open source runs on the people who show up every day. To everyone who reviews pull requests late at night, mentors a first-time contributor, triages a backlog, files issues, or tells us where our tools fall short: thank you. You shaped this feature, and your input is critical in helping us decide what comes next. We’ll keep building with you.