Add blocking rule for excessive PRs or issues - #1087
Merged
Conversation
targos
approved these changes
Aug 13, 2026
Co-authored-by: Brian Muenzenmeyer <brian.muenzenmeyer@gmail.com>
Ethan-Arrowood
approved these changes
Aug 13, 2026
bmuenzenmeyer
approved these changes
Aug 13, 2026
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
4 participants
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.
In a similar spirit as nodejs/node#65250, but is not an option GH offers AFAIK so would be manual moderation action. It's always been the case that sending too many PRs (or too big PRs) would result in you not getting reviews, but because the cost of sending a PR is much lower in the age of coding agents, it's better for the project to desincentivize this behavior as it has a toll on the whole project.