Enforce PR/comments rate-limits for new contributors

Open
#5,473 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
github-actions, python
Domain
devtools

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

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:

Dominant language
Python
Stars
2.7k
Forks
871
Avg merge
1d 10h
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aboutcode-org/scancode-toolkit

All issues in aboutcode-org/scancode-toolkit

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.