Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Configure pull request limit for users without write access

Open
#1,084 18 comments 9 reactions 0 assignees View on GitHub

A pull request for this has already been merged.

  • #65250 by @mcollina — merged

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github

Research direction

Start by reviewing the linked GitHub pull-request limit documentation and the collaborator discussion in this issue. Done means reaching a community decision on the limit and documenting or applying the selected repository setting.

Written by the indexing model from the issue text.

Description

tsc-agenda

The open pull request count on nodejs/node has grown beyond 1000+. A portion of these are from individual contributors who have a high number of open PRs at the same time, which places demands on finite collaborator review capacity.

GitHub provides a setting to limit the number of open pull requests from users without write access. This helps balance the need for open contribution with the reality of limited human review resources.

Proposal

Should we set a pull request limit for users without write access?

This idea was discussed among collaborators, and 5 was suggested as a reasonable starting point.
We'd like to hear broader community input before making a decision.

Rationale
  • Every open PR requires collaborator time for review, feedback, and follow-up. A high volume of open PRs from a single contributor can reduce the time available to review contributions from others.
  • With the rise of AI-assisted tooling, it is now easier than ever to generate pull requests at a higher frequency, which can outpace the capacity of human reviewers.
  • A limit encourages contributors to prioritize their most impactful changes and work with collaborators to get existing PRs merged or closed before opening new ones.
  • It also serves as a backstop against automated spamming attacks that open multiple PRs.
  • Contributors who are consistently engaged at a level that requires more open PRs would be candidates for collaborator status, which is not subject to the limit.
Notes
  • The limit applies only to users without write access. Collaborators are not affected.
  • We can start with 5 (or some other number based on consensus) and re-evaluate based on feedback.
  • GitHub also provides a "bypass list" but we propose not using it to avoid the overhead of managing additions and removals.
Dominant language
JavaScript
Stars
202
Forks
183
Avg merge
13d 12h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodejs/admin

All issues in nodejs/admin

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.