Add Stale Issue / PR GitHub Action #1617
Conversation
MSNev
commented
Jul 22, 2021
MSNev
commented
- Starting with high values because we have not had this before
- Initial values should be 300 days => stale and 30 days => close
MSNev
requested review from
trask,
ramthi,
lzchen,
xiao-lix,
hectorhdzg,
kryalama and
Karlie-777
- Starting with high values because we have not had this before - Initial values should be 300 days => stale and 30 days => close
| days-before-close: 30 | ||
| stale-issue-label: 'stale' | ||
| stale-pr-label: 'stale' | ||
| close-issue-label: 'closed' |
There was a problem hiding this comment.
I don't think closed issues/prs need a label.
There was a problem hiding this comment.
I added this so that we can track (at least initially) the set of issues / PR's that get closed automatically vs all of the others that we have and will close manually (which won't have these labels). According to the documentation the action will also remove this if it gets re-opened.
So eventually (once we are in a much better sate) I agree this will not be needed but as we currently have 117 open (most of which I expect will eventually get closed by this) and 622 Closed I want an easier way to identify these auto-closed items.
| stale-issue-label: 'stale' | ||
| stale-pr-label: 'stale' | ||
| close-issue-label: 'closed' | ||
| close-pr-label: 'closed' |
There was a problem hiding this comment.
I would add a message instead on automatic close. See OpenTelemetry
There was a problem hiding this comment.
We already have a message for when it goes stale, which when closed would be the last message. So I don't think that it's necessary...
I think that by using the label it's a bit more concise and also more searchable without getting false positive matches.
