Enforce PR/comments rate-limits for new contributors

Abierto
#5,473 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
github-actions, python
Área
devtools

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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:

Lenguaje dominante
Python
Estrellas
2.7k
Forks
871
Merge medio
1 d 10 h
PR fusionados (30 d)
3

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de aboutcode-org/scancode-toolkit

Todos los issues de aboutcode-org/scancode-toolkit

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.