Enforce PR/comments rate-limits for new contributors
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- Over a week
- Newbie friendliness
- 12/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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:
- Dominant language
- Python
- Stars
- 2.7k
- Forks
- 871
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 3
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aboutcode-org/scancode-toolkit
-
yarn.lock v1 with a scoped alias of an unscoped package yields no packages and no errorPossibly taken @Shubham-dev-stack claimed this 6 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
aboutcode-org/scancode-toolkit#5466 ·
Maintainers usually reply within 2 days
-
package-lock.json dependencies report file_references as a list inside a listPossibly taken @Anbarasu2410 claimed this 9 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aboutcode-org/scancode-toolkit#5449 · 4 comments ·
Maintainers usually reply within 2 days
-
scancode aborts when encountering a broken RPM archivePossibly taken @Ashutosh-Panda2004 claimed this 14 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
aboutcode-org/scancode-toolkit#5407 · 3 comments ·
Maintainers usually reply within 2 days
-
Four silent bugs: IsRequiredPhrase.license_expression returns None, find_in_path ignores later PATH changes, duplicate dict keys override license mappingsPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 Half a day Newbie friendliness 65/100
aboutcode-org/scancode-toolkit#5405 · 1 comment ·
Maintainers usually reply within 2 days
-
parse_maintainer_name_email returns empty name and wrong email when string has "@" but no angle bracketsPossibly taken @RohitSutar1823 claimed this 14 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
aboutcode-org/scancode-toolkit#5402 ·
Maintainers usually reply within 2 days
All issues in aboutcode-org/scancode-toolkit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mohanraj00/entelos#200 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
sweep
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
bketelsen/truenas-mcp#77 ·
Maintainers usually reply within 1 day
-
Console writes URL credentials to the local log, though AGENTS.md says secrets never reach diskOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
sandbox-quantum/switch#2163 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
openedx/xblock-lti-consumer#765 ·
Maintainers usually reply within 1 day