GitHub: add actions/stale to keep the GitHub backlog tidy #18074
Conversation
|
@chennes @yorikvanhavre is this ok for you? |
|
It's fine with me. We could consider a wider discussion at the next developer meeting. |
|
waiting for developer meeting discussion |
|
Paused waiting for Dec 1 dev meeting. |
|
Hi @maxwxyz |
|
@marcuspollio some of the authors are currently away but plan to resolve it soon, maybe not close them automatically but just add a label? |
|
Yes, the idea for PR would be about the same as for issues. After say 4-6 months of inactivity, send an automatic "Hi! This Pull Request hasn’t seen activity in a while..." and add some status. Then, after say 2-3 more months if not action or comment, close it. |
Adding the actions/stale to help keep the GitHub repository organized and automatically identify/close stale issues.
Two actions to be implemented:
Check for issues without any feedback (comment) in the last 90 days (confirmed bugs, high priority issues and feature requests are not touched by this) to check for relevance.The issue was confirmed by others
,
Priority: High
,
Priority: Critical
Needs a fix ASAP
,
Blocker
Issue is a release blocker
,
Type: Feature
FR for improvements or new features
This checks all issues but not the ones with the labels Status: Confirmed
Check for issues where feedback was requested but no feedback was provided in the last 20 daysMissing required feedback from user or dev
,
Status: Needs test on dev version
Missing test on the weekly version in safe mode
,
Status: Needs steps to reproduce
Missing steps to reproduce or macro file
This only checks on issues with the tags: Status: Needs feedback
In both cases if an issue is considered stale it is automatically tagged Status: StaleStale and might be closed automatically.
and a comment is added asking for further feedback.
If no follow up comment is provided in the following 20 days, the issue is automatically closed.
The action runs every day.
We could add other actions later on too.