Configure pull request limit for users without write access
已经有一个关联 PR 被合并了。
- #65250 来自 @mcollina —— 已合并
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- github
调研方向
首先查看链接的 GitHub pull request 限制文档,以及此 issue 中与协作者的讨论。完成的标准是就该限制达成社区决定,并记录或应用所选的 repository 设置。
由索引模型根据 Issue 内容生成。
描述
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.
- 主要语言
- JavaScript
- 星标
- 202
- 派生
- 183
- 平均合并
- 13 天 12 小时
- 30 天内合并 PR
- 2
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
nodejs/admin 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 90/100
-
tsc-agenda
难度 5/5 一周以上 新手友好度 30/100
-
难度 5/5 一周以上 新手友好度 35/100
-
难度 5/5 一周以上 新手友好度 35/100
-
难度 5/5 一周以上 新手友好度 30/100
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
antfu-collective/icones#398 ·
-
ECmail.com 未关闭
难度 1/5 1 小时以内 新手友好度 90/100
wesbos/burner-email-providers#554 ·
-
难度 2/5 1-3 小时 新手友好度 65/100
radiantearth/stac-browser#1023 ·
-
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 2/5 1-3 小时 新手友好度 75/100
components-web-app/docs#92 ·