Limit open pull requests from outside contributors on GitHub

Can I limit how many open pull requests outside contributors can have on my GitHub repo

Yes. On a public GitHub repository, you can set a maximum number of concurrent open pull requests for users without write access. When they hit the limit, they must close or merge one of their open pull requests before opening another. GitHub documents this under repository interaction limits.

The rule is narrow. It applies to users without write access, not to collaborators or other users with write access. Draft pull requests do not count toward the limit, only open non-draft pull requests do. That detail matters if someone opens work-in-progress branches and expects the counter to move.

You set it in the repository settings, under Moderation options, then Interaction limits. GitHub shows a specific pull request limit control there, and you choose the maximum number allowed. The same page also lets you keep trusted contributors on a bypass list instead of granting them full collaborator access.

The part people get wrong is assuming this is a general GitHub-wide cap or a private-repo control. GitHub describes it for public repositories, and it is about concurrent open pull requests, not total pull requests over time. A contributor can still open one, close it, and open another later if they stay under the active limit.

The inconvenient part is that the limit does not solve every kind of noise. It blocks the same person from stacking too many active pull requests, but it does not stop low-quality submissions, spammy titles, or review churn. GitHub’s broader moderation tools still matter, including temporary interaction limits, code review limits, blocking users, and locking conversations when needed.

If your goal is to slow down drive-by contribution volume without closing the door, the pull request limit is the right control. If your goal is to manage a heated repository, GitHub’s temporary interaction limits are separate and broader, because they can restrict creating pull requests, opening issues, commenting, and more for a limited time.

A practical setup is to set a low cap for the general public, then put reliable external contributors on the bypass list. GitHub says the bypass list is available through the UI or the API, and it supports up to 100 users. That keeps a contributor productive without giving them full write access.

If you also want to reduce review bottlenecks, combine the pull request limit with CODEOWNERS, branch protection, or merge queue rules. GitHub’s docs separate those features, which is useful because they solve different problems: one controls submission volume, one controls who must review, and one controls merge safety.

The clean answer is yes, you can limit how many open pull requests outside contributors can have. The exact control is the concurrent open pull request limit for users without write access, and GitHub gives you a bypass list for people you trust.

If you want to coordinate testing instead of repo moderation, DevConnect is a separate option for swapping app tests with other builders, and you can see it at https://devconnectplatform.com. GitHub’s pull request limit is still the thing that controls PR volume on the repo itself.