Add Github action to mark issues as stale #7040
Conversation
This uses the [stale action](https://github.com/actions/stale). The intended configuration is: - At 1:30 every day, any issues that have been inactive for 30 days are: - Labelled stale, and - Have a comment posted explaining why they're stale and requesting an update or that the issue be closed. - Labels pertaining to long-term items, feature requests, and good first / second issues do not get marked. - Stale issues are never closed.
|
@gmarkall thank you for looking into this. FWIW: some time ago we had attempted something similar: IIRC we encountered some serious issues related to filtering of labels and selecting issues and PRs that are never tobe marked as stale. Further IIRC this was related to bugs within Github that seemed to only manifest when the number of labels was large (like in the Numba repo). Even further IIRC I reached out to Github about this issue, they actually responded several times mentioning that they could reproduce it and were working on it but have gone radio-silent since then. |
|
@esc thanks for the comments - #6225 looks like it's using something different - the Github Stale app based on Probot seems to be distinct from the Stale action that this uses. Do you have any idea if the bugs in Github were generic related to labels, or were they problems with that app? (FWIW, I note that other projects such as the RAPIDS ones seem to be able to make use of the Stale action on which this PR is based, but I've no direct experience managing / running that) |
|
Here are some screenshots from my interactions with GitHub, I'v reached out again today. Sorry that the order is a bit messed up, please use the dates of each message to accurately reconstruct the flow (but all the messages are there).
|
|
Would add:
And what about the ones with a numerical prefix? Like '0 - Backlog' |
esc
added
5 - Ready to merge
This uses the stale action.
The intended configuration is: