New release: you can now set pull requests limits at the organization level

[moraesc]

As low-quality contributions continue to increase, we’re giving maintainers more ways to manage incoming pull requests and protect their teams’ time.

With the new organization-level pull request limits, organizations can control how many pull requests users without write access can open across their repositories. This eliminates the need to configure limits repository by repository, making it easier to apply a consistent contribution policy at scale.

This is another step toward helping maintainers keep contributions manageable while preserving an open path for the broader community to participate.

We'd love to hear your feedback. Drop a comment with any questions or thoughts!

[ankush850]

GitHub added a feature that lets organizations set pull request (PR) limits across the entire organization all at once, instead of configuring them repo by repo.

Key takeaway:

What it does: Restricts how many open PRs a user (without write access) can have open across all repositories in your organization.

Why they added it: To stop people from spamming open-source organizations with low-quality PRs and to save maintainers time.

[MikeMcC399]

Hi @moraesc

This is generally a great addition to the toolset for moderators!

We're finding though that always displaying the limit looks like the open quota number is the norm, not the exception. Could it be made a option to only display a warning when a user gets close to the limit of open PRs or exceeds it?

We're finding that some users with automation tools are interpreting the limit as an invitation (or at least justification) to open as many PRs as possible, and sometimes in such a short period of time that reviewers are completely overwhelmed!