Document concurrent PR limit for non-collaborators#44711
Open
moraesc wants to merge 5 commits into
Open
Conversation
Add documentation for the new repository setting that allows maintainers to set a maximum number of concurrent open pull requests for non-collaborators, including the trusted contributor allowlist. Closes github/docs-content#22348 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
github-actions
Bot
added
the
triage
Contributor
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates the “Limiting interactions” documentation to also cover limiting concurrent open pull requests for non-collaborators.
Changes:
- Expanded the page intro and permissions frontmatter to mention pull request limits.
- Added a new section explaining PR limits for non-collaborators, allowlisting, and configuration steps.
Show a summary per file
| File | Description |
|---|---|
| content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md | Documents a new moderation control for limiting concurrent open PRs and updating page metadata accordingly. |
Copilot's findings
- Files reviewed: 1/1 changed files
- Comments generated: 5
- Revert frontmatter intro and permissions to concise originals; PR limit details now live in the body content - Add 'In a public repository' to the PR limit section to align with the page scope - Remove duplicated navigation steps; reference the earlier section instead to create a single source of truth Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Comment on lines
+36
to
+38
| In a public repository, you can also set a maximum number of pull requests that a user without write access can have open at the same time. When a user without write access reaches the limit, they must close or get an existing pull request merged before they can open a new one. | ||
|
|
||
| This setting helps maintainers manage contribution volume by preventing users from opening an excessive number of pull requests, which can overwhelm review queues and trigger unnecessary CI runs. The limit only applies to users without write access — users with collaborator access to the repository are not affected. |
|
|
||
| ## Limiting concurrent open pull requests for users without write access | ||
|
|
||
| In a public repository, you can also set a maximum number of pull requests that a user without write access can have open at the same time. When a user without write access reaches the limit, they must close or get an existing pull request merged before they can open a new one. |
|
|
||
| ### Adding trusted contributors to the bypass list | ||
|
|
||
| Rather than granting full collaborator access, you can add trusted contributors to a bypass list, allowing them to exceed the pull request limit while keeping their permissions otherwise unchanged. This is ideal for regular external contributors who routinely open multiple pull requests but don't need the additional permissions that come with collaborator access. |
Comment on lines
+50
to
+51
| 1. Under "Pull request limits", select the maximum number of concurrent open pull requests allowed for users without write access. | ||
| 1. Optionally, to allow specific users to bypass the limit, under "Bypass list", search for and select the users you want to add. |
- Fix contradictory exemption wording: 'users with write access or
higher' instead of 'users with collaborator access'
- Replace 'close or get' with 'close or have' for clarity
- Replace contractions ('don't') with 'do not' per docs style
- Use bold formatting (**Pull request limits**, **Bypass list**)
instead of quotes for UI elements, matching page conventions
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does
Adds documentation for the new repository interaction limit setting that allows maintainers to set a maximum number of concurrent open pull requests for non-collaborators. This includes:
Why
Open source maintainers need a proactive tool to manage the growing volume of low-quality, drive-by pull requests. This setting lets them cap concurrent open PRs per non-collaborator while providing an allowlist for trusted external contributors.
Related
Note
The exact UI labels (e.g., "Pull request limits", "Allowlist") in the procedural steps should be verified against the shipped UI and updated if they differ.