First pass stale MRs prompt
What does this MR do and why?
First pass stale MRs prompt
- Identify MRs that are over 1 year old with no comments in the past 6 months and mark as vintage
- Locate vintage MRs and mention the author with the following message and add the stale label
Hi {{author}} :wave:,
This merge request has been identified as it has an age of over 1 year with no comments in the last 6 months
Please could you check it over to see whether any of the following actions can be taken:
- Progress the merge request towards completion
- Close the merge request down
- 1 weeks later attempt to either:
- 3a. Ping the EM and remove the stale label if the MR has been updated with the following message
Hi #{em_for_team} :wave:,
This MR was logged as stale, but there has comments since we prompted for action.
Please could you check it over to see whether any of the following actions can be taken:
- Progress the merge request towards completion
- Close the merge request down
If you wish to prevent further automatic closure, please apply the ~automation:prevent-auto-close label
3b. Close the stale MR if no updates have been made with the following message
Hi {{author}} and #{em_for_team} :wave:,
Due to there being no activity on this stale MR in 1 weeks. This MR will be automatically closed
If you wish to reopen and prevent further automatic closure, please reopen and apply the ~automation:prevent-auto-close label
flowchart
graph TD
init(Community contribution) -- Older than 365 days --> vintage
vintage -- No comments in 180 days --> hasPrevention{{Has automation:prevent-auto-close?}}
hasPrevention -- Yes --> vintage
hasPrevention -- No --> pm{{Ping author}}
pm --> stale
stale -- 1 week later --> hasComments{{Has comments within 7 days?}}
hasComments -- Yes --> pem{{Ping EM}}
hasComments -- No --> pboth{{Ping author and EM}}
pem -- Hint automation:prevent-auto-close --> vintage
pboth -- Hint automation:prevent-auto-close --> closure
Expected impact & dry-runs
These are strongly recommended to assist reviewers and reduce the time to merge your change.
Action items
-
(If applicable) Add documentation to the handbook pages for Triage Operations => - (If applicable) Identify the affected groups and how to communicate to them:
-
/cc @ person_or_group
=> -
Relevant Slack channels => -
Engineering week-in-review
-
References
Edited by Lin Jen-Shin