Enforce PR/comments rate-limits for new contributors

未关闭
#5,473 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
一周以上
新手友好度
12/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
github-actions, python
领域
devtools

调研方向

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 内容生成。

描述

maintainers-only

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:

Some repos which could be useful:

主要语言
Python
星标
2.7k
派生
871
平均合并
1 天 10 小时
30 天内合并 PR
3

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

aboutcode-org/scancode-toolkit 的其他 Issue

查看 aboutcode-org/scancode-toolkit 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。