This repository was archived by the owner on Oct 1, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 243
PR and issue management
Ben McMorran edited this page Jan 8, 2022
·
5 revisions
PRs are reviewed at least weekly. We currently don't get a large number of PRs, so the review process is not automated. Simply look at the list of active PRs, merge what's ready, and leave feedback where changes are needed. If any changes require a broader design discussion, feel free to loop in others from the team.
Issues are triaged at least weekly following this workflow. The goal is to keep the list of active issues short, actionable, and easy to query.
-
Query for all issues with the
needs-more-infolabel. These are existing issues that require more information from the creator to be actionable.- If the creator has responded to the request for information, remove the
needs-more-infolabel and follow the triage process in step 2. - If the creator has not responded, leave the issue as-is. Automation will eventually close the issue if there is no response.
- If the creator has responded to the request for information, remove the
-
Query for all issues with the
triagelabel. These are new issues that have not yet been triaged.- If the issue is a duplicate, has already been fixed, or will never be actionable or fixed, close the issue and leave a comment explaining why it was closed.
- If the issue is not actionable because it's missing details like repro
steps, ask the creator for the relevant details, remove the
triagelabel, and add theneeds-more-infolabel. - If the issue is actionable, simply remove the
triagelabel. If there is additional context that would be helpful for the creator, like a workaround or related issue, feel free to leave a comment.
A few bits of automation powered by GitHub Actions help support this workflow.
- Every time an issue is opened, the
triagelabel is added to the issue. - Every time an issue is closed, the
triageandneeds-more-infolabels, if present, are removed. - Issues with the
needs-more-infolabel are evaluated hourly for staleness. If the issue has been inactive for 30 days, a reminder comment is added and thestalelabel is added. If the issue is inactive for another 7 days, a closed comment is added, the issue is closed, and thestalelabel is removed.