Skip to content

Document concurrent PR limit for non-collaborators#44711

Open
moraesc wants to merge 1 commit into
github:mainfrom
moraesc:moraesc/concurrent-pr-limit-for-non-collaborators
Open

Document concurrent PR limit for non-collaborators#44711
moraesc wants to merge 1 commit into
github:mainfrom
moraesc:moraesc/concurrent-pr-limit-for-non-collaborators

Conversation

@moraesc

@moraesc moraesc commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

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:

  • A new section in the "Limiting interactions in your repository" article explaining the feature
  • Documentation for the trusted contributor allowlist that lets specific users bypass the limit
  • Step-by-step instructions for configuring the pull request limit and allowlist

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.

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>
Copilot AI review requested due to automatic review settings June 13, 2026 00:08
@welcome

welcome Bot commented Jun 13, 2026

Copy link
Copy Markdown

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 github-actions Bot added the triage Do not begin working on this issue until triaged by the team label Jun 13, 2026
@github-actions

Copy link
Copy Markdown
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 links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md fpt
ghec
fpt
ghec

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.'
Comment on lines 31 to 32
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 %}
Comment on lines +46 to +49
{% 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.
Comment on lines +36 to +38
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage Do not begin working on this issue until triaged by the team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants