Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Configure pull request limit for users without write access

未關閉
#1,084 18 則留言 9 個 reaction 已指派 0 人 在 GitHub 檢視

已經有一個關聯 PR 被合併了。

  • #65250 來自 @mcollina —— 已合併

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
github

研究方向

首先查看連結的 GitHub pull request 限制文件,以及此 issue 中與協作者的討論。完成的標準是就該限制達成社群決定,並記錄或套用所選的 repository 設定。

由索引模型根據 Issue 內容生成。

描述

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.
主要語言
JavaScript
星號
202
分支
183
平均合併
13 天 12 小時
30 天內合併 PR
2

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

nodejs/admin 的其他 Issue

查看 nodejs/admin 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。