Did GitHub add pull request limits for public repositories

Did GitHub add pull request limits for public repositories

Yes. GitHub added a limit for concurrent open pull requests from users without write access in public repositories, and it also documents activity limits for busy repositories. The part people miss is that this is not a blanket cap on all pull requests, it is a control on who can open how many at once and a separate performance guideline for merge volume.

GitHub’s docs say that in a public repository, you can set a maximum number of pull requests a user without write access can have open at the same time. When that user reaches the limit, they must close or merge an existing pull request before opening another one. GitHub says this helps maintainers manage review volume and avoid unnecessary CI runs.

GitHub also documents repository-level pull request activity guidance for high-traffic repos. Its repository limits page recommends staying within 1,000 open pull requests against the same branch, and it recommends a merge rate of 1 merged pull request per minute. Those are guidance limits for performance and stability, not a product-wide rule that blocks ordinary public repositories.

The part people get wrong is mixing up three different settings. One setting limits how many pull requests a user without write access can keep open. Another setting limits who can approve or request changes in reviews. A third set of docs describes interaction limits that can temporarily restrict users from commenting, opening issues, or creating pull requests.

If you only want the shortest practical answer, use this one: GitHub did add a public-repository pull request limit, but it is a configurable per-user concurrency limit, not a hard cap on all public pull requests. For the exact setting and where it appears in the UI, GitHub’s docs are the source of truth, and the change is documented in GitHub’s own repository interaction pages and changelog.

What the limit affects matters. It applies to users without write access in a public repository, so maintainers and collaborators are not blocked in the same way. A contributor can still participate by closing one pull request and opening another, or by getting write access if that is appropriate for the project.

The inconvenient part is that the limit does not solve review bottlenecks by itself. If a repository is already overloaded, a low open-PR cap can push contributors to bundle more changes into one pull request, or force them to wait until old work is closed. That can reduce noise, but it can also make triage less flexible if the team has not set clear contribution rules.

GitHub’s repository limits page also makes clear that pull request load is about repository health, not just policy. Many open pull requests against the same branch can slow mergeability checks and cause timeouts. In busy repositories, the practical fix is usually process, branch discipline, or merge queue settings, not just a stricter limit.

The review-limit setting is different again. In public repositories, GitHub says anyone can comment on pull requests, but only people with read access or higher can approve or request changes when code review limits are enabled. That setting controls review authority, not how many pull requests can be opened.

If you are checking a repo right now, look in repository Settings, then Moderation options. GitHub’s interaction-limits docs show the path for limiting concurrent open pull requests for users without write access. If the repo uses organization-level interaction limits, those can apply across public repositories owned by the organization.

If your question came from a contributor hitting a new wall, the first thing to verify is which limit fired. A user can be blocked because they hit the concurrent open pull request cap, because an interaction limit is active, or because the repository has review restrictions. Those produce different behavior and need different fixes.

For a maintainer, the clean rule is simple: use the concurrent open pull request limit when you want to slow down repeated open PRs from the same outside account, and use review limits or interaction limits when you want to control approval rights or temporary disruption. GitHub documents each of those separately, and the settings do different jobs.