Document concurrent PR limit for non-collaborators#44711
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. |
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. |
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
| --- | ||
| title: Limiting interactions in your repository | ||
| intro: You can temporarily enforce a period of limited activity for certain users on a public repository. | ||
| intro: You can temporarily enforce a period of limited activity for certain users on a public repository, and set a maximum number of concurrent open pull requests for non-collaborators. |
| fpt: '*' | ||
| ghec: '*' | ||
| permissions: 'People with admin permissions to a repository, and organization moderators, can temporarily limit interactions in that repository.' | ||
| permissions: 'People with admin permissions to a repository, and organization moderators, can temporarily limit interactions in that repository and set a maximum number of concurrent open pull requests for non-collaborators.' |
| 1. In the sidebar, select **{% octicon "comment-discussion" aria-hidden="true" aria-label="comment-discussion" %} Moderation options**, then click **Interaction limits**. | ||
| {% data reusables.community.set-interaction-limit %} |
| {% data reusables.repositories.navigate-to-repo %} | ||
| {% data reusables.repositories.sidebar-settings %} | ||
| 1. In the sidebar, select **{% octicon "comment-discussion" aria-hidden="true" aria-label="comment-discussion" %} Moderation options**, then click **Interaction limits**. | ||
| 1. Under "Pull request limits", select the maximum number of concurrent open pull requests allowed for non-collaborators. |
| You can set a maximum number of pull requests that a non-collaborator can have open at the same time in your repository. When a non-collaborator 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 non-collaborators — users with collaborator access to the repository are not affected. |
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.