-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automate keeping reviewers list up-to-date #974
Comments
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
/remove-lifecycle rotten |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
We should introduce automation to help us add new reviewers to the org who are meeting reviewer requirements based on the contributor ladder, and move inactive reviewers to alumni if they meet the criteria for inactive reviewers. Org updates should go through human review and notify the contributors involved, but we should create automation for proposing changes.
Adding new reviewers is important because it encourages contributors to grow their contributor status, spreads the load among reviewers, and removes the awkwardness of "nominating" yourself for increased privileges. Removing inactive reviewers is important because it helps prevent PRs from going unreviewed and granting overly lax permissions on our repos.
The best place to start would be modifying https://gist.github.com/dibyom/83651e34488aa3acaf38be4e1ba80e45 and https://gist.github.com/afrittoli/8aa0e878a87652f785bb9e5ec4c98400 to create a script in the community repo that can print out suggested new reviewers and suggested alumni. (Note: GitHub contributions summaries are already publicly available on the contributor dashboard).
After this, we could optionally try automating running the script on a ~ monthly basis for the Pipelines repo and publishing the results somewhere visible to Pipelines maintainers (e.g. a slack channel or just opening a PR directly).
The text was updated successfully, but these errors were encountered: