Stale bot should tag issues it closes with a unique tag!

[david-bakin]

Currently issues closed by the stale bot just get closed (and it isn't even the stale bot which is shown as the closer!) The stale bot should tag issues that it closes with a unique tag so they can be searched for (and triaged!) (or have the never stale tag applied if appropriate!)

Unless the query is:closed label:"meta: stale" is supposed to be sufficient ...

[gtsiolis]

Thanks for the proposal, @david-bakin!

I agree, there's benefit is marking issues closed from the stale bot with a unique label but the ~meta: stale label would suffice for now as stale bot automatically adds this before closing an issue, see relevant query and example comments[1][2].

thought: We've only scratched the surface of automatic triage operations like this so far, in the future using a more specific label, following the proposal here, like ~meta: auto-closed could be ideal but this would require us first to get better and more intentional about issue triaging.

issue: From what I've seen, the stale app does not support this, see relevant pull request. Let me know if you know a workaround to do this with the stale app.

suggestion: FWIW, I don't think the stale app[3] currently used is flexible or powerful enough to support more complex use cases, especially as an inactive project. Moving to something like the stale action[4], which already supports close-issue-label, or a custom solution build to match our needs sounds like the best way forward.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.