GitHub’s pull request limits reduce maintainer noise effectively

Open source thrives when contributors collaborate, but unchecked volume can drown out meaningful work. GitHub introduced pull request limits to help maintainers manage rising noise without shutting the door on potential fixes.

Maintainers say the change restores balance to their workflows. Instead of sifting through dozens of half-finished proposals, they now see fewer but more deliberate pull requests. This shift doesn’t eliminate contributions—it sharpens their quality by forcing contributors to prioritize what really matters.

Why GitHub introduced pull request limits

Reviewing a pull request still requires human time, but creating one has never been easier. In January 2023, developers merged about 25 million pull requests monthly across GitHub. By comparison, the total now exceeds 90 million—a 3.6-fold increase. While most submissions come from well-intentioned developers, the sheer volume overwhelms volunteer maintainers.

GitHub’s new limits let repository owners cap how many open pull requests non-writers can have at once. Once the cap is hit, contributors must close or merge an existing request before opening another. Draft pull requests and AI-generated submissions (like those from Copilot) count toward the limit, but trusted contributors can be added to a bypass list without granting full write access.

Real-world impact on maintainers

Contributors and maintainers report immediate improvements. Nicholas Tindle, from AutoGPT, says the change reduces frustration: "It’s helped us want to review pull requests again. Knowing that someone hasn’t just opened 5–10 pull requests that are slop makes it much easier to want to look."

Homebrew’s Mike McQuaid highlights a persistent issue: "We’ve had problems 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."

OpenClaw’s Vincent Koc adds: "We get a huge volume of pull requests from the community and had to build our own bots for fighting spam. We are super glad GitHub has been able to develop out-of-the-box solutions for maintainers now to manage this volume."

What’s next: expanding contribution controls

Pull request limits are just the beginning. GitHub is rolling out additional tools to give maintainers finer control over their workflows.

• Archiving pull requests (shipping soon): Repository admins will soon hide low-quality or spammy pull requests behind an archive. These remain accessible to admins but are filtered out of the default view, preserving context without clutter.

• Issue limits (in development): Similar caps will apply to issues, limiting how many open issues non-writers can create per repository. Bypass lists and collaborator-only creation options will mirror pull request controls.

• Smarter bypass signals (up next): Future updates aim to automate trust management. Instead of manually curating bypass lists, maintainers could rely on real signals like a previously merged pull request, account age, or organization membership to grant automatic exemptions.

• Cross-repository controls (exploring): A single-repository cap helps with concentrated activity, but it doesn’t address contributors spreading pull requests across hundreds of projects. GitHub is testing ways to detect and manage such behavior using trust signals or rate limits.

A thank you to open source contributors

Behind every open source project are people who dedicate time to reviewing code, mentoring newcomers, and maintaining systems. Your feedback shaped these new limits, and your input remains critical as GitHub refines its tools. The pull request queue isn’t just a feature—it’s a community, and every contribution helps keep it alive.

Try enabling pull request limits in your repository settings today. Share your experience and help shape the next improvements.