Exclude confirmed bugs from stale bot#30921
Conversation
|
I appreciate the argument, but I believe this workflow has helped us to close more confirmed bugs "the right way" than automatically. So far, 41 confirmed bugs that were labelled by this workflow have subsequently been closed. Of these, only 13 were closed by the bot (have the "status: closed as inactive" label). The other 28 we either verified no longer exist, we decided they were "won't fix" or we actually fixed them via PR. I argue that we wouldn't have looked at and closed all 28 of these if the bot had not surfaced them, they would still be forgotten in the backlog. Practically, although this workflow is designed to auto-close, I do not think it ever does in practice1 because we have it set up to look at least recently updated issues first and we also limit it so it doesn't generate too many notifications each run. So we created the stale-tidy workflow to actually do the closing (and remove the label if someone comments). So a compromise might be to have this workflow continue to label and comment on the confirmed bugs (so we get reminded about them) but change Footnotes
|
We should not close confirmed bugs through a timeout mechanism. The bug exists and should be tracked as open bug as long as we don't fix it or explicitly decide to not handle this, in which case, we'd manually close as "won't fix".
311157d to
b9b5d62
Compare
Done. This is is the best compromise. |
We should not close confirmed bugs through a timeout mechanism. The bug exists and should be tracked as open bug as long as we don't fix it or explicitly decide to not handle this, in which case, we'd manually close
as "won't fix".