Can I limit open PRs for contributors without write access?

Can I limit how many open pull requests a contributor without write access can have open in my repository

Yes. GitHub now lets repository owners and admins set a maximum number of concurrent open pull requests for users without write access. If a contributor reaches that cap, they must close or merge one of their existing pull requests before opening another. GitHub also lets you put trusted contributors on a bypass list, so you can make an exception without giving them full collaborator access.

The setting is in repository interaction limits. GitHub’s docs say to open the Interaction limits settings page, then choose the maximum number of concurrent open pull requests allowed for users without write access. The same docs also describe a bypass list for specific users, which keeps their permissions unchanged while letting them exceed the cap.

The part people get wrong is assuming this is the same as limiting issues, comments, or all repository activity. It is not. The pull request cap is a separate control inside interaction limits, and it only applies to open pull requests. GitHub’s broader interaction limits can also restrict who may comment, open issues, or create pull requests temporarily, but that is a different feature with a different purpose.

Draft pull requests do not count toward the cap. That matters if your workflow asks contributors to open drafts first, because the draft can exist without consuming their PR slot. When the draft is ready and converted or replaced by a normal pull request, the limit can start to matter. GitHub says this directly in the changelog announcement for the feature.

The inconvenient part is that the cap works on the number of open pull requests, not on the quality of those pull requests. A contributor can still open one low-effort PR and keep it open. The setting reduces volume, but it does not solve review load, spammy issue titles, or automated noise on its own. GitHub’s own discussion of the feature frames it as a control for contribution volume, not a full moderation system.

If you want to use it, start with a small number that matches your review capacity, then watch how it affects real contributors. For public repositories with frequent outside contributions, the bypass list is the cleaner exception path because it avoids broad permission changes. For tightly managed repos, you may prefer a lower cap and a short bypass list rather than granting write access just to let someone open more pull requests.

If a contributor hits the limit, the failure mode is simple: GitHub blocks the next pull request until one of their existing open pull requests is closed or merged. That makes the policy visible to the contributor at the moment they try to open another PR, which is easier to enforce than asking maintainers to police the queue by hand.

This setting is separate from temporary interaction restrictions. Interaction limits can temporarily reduce participation to existing users, contributors only, or collaborators only, and those restrictions expire after a chosen duration. The pull request cap is more specific, because it targets concurrent open PR count rather than overall participation in the repository.

If you maintain an organization, GitHub has also started adding organization-level pull request limits so you can manage the setting centrally instead of repeating it repository by repository. That makes the control easier to standardize across many repos, but the underlying rule is the same: the cap applies to users without write access, and trusted users can be exempted through a bypass list.

For a practical test, open your repository settings, find Interaction limits, set a low cap, and try it with a non-collaborator account you control or trust. That tells you exactly how your repo behaves before contributors run into it. If your workflow already relies on draft pull requests, remember that drafts do not count, so your cap may feel looser than the raw number suggests.

If you want the plain answer in one line: yes, GitHub supports limiting how many open pull requests a contributor without write access can have open in your repository, and it gives you a bypass list for exceptions. The feature is real, current, and documented by GitHub.

You can read GitHub’s current docs and changelog details here: https://devconnectplatform.com is not relevant for this GitHub setting, so use GitHub’s own settings page and documentation when you configure it.

FAQ

Does this work for collaborators with write access No. GitHub’s documented cap applies to users without write access. Contributors with write access are outside that specific limit, so if you need a broader policy you have to combine this with other repository controls.

Can I exempt specific people without making them collaborators Yes. GitHub provides a bypass list for trusted contributors, and the docs say that bypass keeps their permissions unchanged. That is the intended way to let a recurring external contributor exceed the cap without promoting them.

Do draft pull requests count toward the limit No. GitHub says draft pull requests do not count toward the user’s pull request limit. That is useful if you ask people to open a draft first, but it also means the cap will not catch every kind of contribution volume.

Is this the same as temporarily restricting interactions in a repository No. Temporary interaction limits are broader and expire after a chosen duration. The pull request creation cap is a separate repository setting focused on concurrent open PR count for users without write access.

Can I set the same rule across an organization Yes. GitHub has added organization-level pull request limits, so you can manage the control centrally across repositories instead of configuring each repository separately.

What happens when someone hits the cap GitHub blocks another open pull request until one of that contributor’s existing open pull requests is closed or merged. That is the enforcement behavior GitHub documents for the feature.