Enforce PR/comments rate-limits for new contributors
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
This is an org-wide policy discussion rather than a code change: the body lists candidate automations (PR limits for new contributors, auto-closing stale or failing PRs, comment rate limits, first-interaction reminders) and links GitHub's built-in PR-limit and interaction-limit features. Nothing in the payload names a file, test or entry point, so start by deciding which policies the maintainers want. Done means an agreed list of policies and a chosen mechanism, such as GitHub settings or a workflow, before any implementation.
由索引模型根据 Issue 内容生成。
描述
Here we need to both deccide on org-wide policies and implement them through automation.
Things we could potentially implement:
- rate limiting PRs from new contributors (maybe 2/3 open PRs at a time, if they do not have any merged PRs already)
- auto close non-draft PRs with failing tests (if there aren't test failures on main branch)
- auto close PRs open for too long without updates after changes are requested
- rate limiting comments for new contributors
- remind new contributors of contributing guidelines/policy on their first interaction
- remind contributors with comments in issues which are already assigned to a person/project already, or labeled as such
Github has some basic features which can be used, but are likely not enough:
- How pull request limits are cutting down the noise (GitHub Blog)
- Pull request limits: Exempt contributors by age or history (GitHub Changelog)
- Limit open pull requests for users without write access (GitHub Changelog)
- Set pull request limits at the organization level (GitHub Changelog)
- Limiting interactions in your organization (GitHub Docs)](https://docs.github.com/en/enterprise-cloud%40latest/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)
Some repos which could be useful:
- 主要语言
- Python
- 星标
- 2.7k
- 派生
- 871
- 平均合并
- 1 天 10 小时
- 30 天内合并 PR
- 3
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
aboutcode-org/scancode-toolkit 的其他 Issue
-
yarn.lock v1 with a scoped alias of an unscoped package yields no packages and no error可能已有人在做 @Shubham-dev-stack 于 6 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 74/100
aboutcode-org/scancode-toolkit#5466 ·
维护者通常 1 天内回复
-
package-lock.json dependencies report file_references as a list inside a list可能已有人在做 @Anbarasu2410 于 9 天前认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 82/100
aboutcode-org/scancode-toolkit#5449 · 4 条评论 ·
维护者通常 1 天内回复
-
scancode aborts when encountering a broken RPM archive可能已有人在做 @Ashutosh-Panda2004 于 14 天前认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 62/100
aboutcode-org/scancode-toolkit#5407 · 3 条评论 ·
维护者通常 1 天内回复
-
Four silent bugs: IsRequiredPhrase.license_expression returns None, find_in_path ignores later PATH changes, duplicate dict keys override license mappings可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭bug
难度 2/5 半天 新手友好度 65/100
aboutcode-org/scancode-toolkit#5405 · 1 条评论 ·
维护者通常 1 天内回复
-
parse_maintainer_name_email returns empty name and wrong email when string has "@" but no angle brackets可能已有人在做 @RohitSutar1823 于 15 天前认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 84/100
aboutcode-org/scancode-toolkit#5402 ·
维护者通常 1 天内回复
查看 aboutcode-org/scancode-toolkit 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 76/100
GoogleCloudPlatform/professional-services-data-validator#1899 ·
维护者通常 4 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
mohanraj00/entelos#200 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 68/100
-
sweep
难度 2/5 1-3 小时 新手友好度 85/100
bketelsen/truenas-mcp#77 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 86/100
sandbox-quantum/switch#2163 ·
维护者通常 1 天内回复