chore: close issues with no user response#1804
Conversation
JaffaKetchup
left a comment
There was a problem hiding this comment.
I have mixed feelings about this. We previously had this stale bot (admittedly without the tag exception rules), but it was a bit of a pain. Even if 50% of bug reports without enough information are invalid, that still leaves 50% that would be better investigated. Leaving them open allows other people to find issues and add their own info.
Would like some input from the others (@ibrierley, @TesteurManiak, @mootw).
|
(There is currently one problem with this PR: The
I'm aware that this was used in the past. While it was configured to close all issues in the past, this pr gives automation for the Having some kind of automation around #1760 is a good example what happens if we don't have this automation.
It wouldn't make sense for us to tag those other 50% of valid bug reports with
It is still possible for other people to adopt such issues. As soon as an update gets posted the |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
JaffaKetchup
left a comment
There was a problem hiding this comment.
Two minor changes to wording, let me know what you think of them.
Co-authored-by: Luka S <github@jaffaketchup.dev>
* Update issue-comment.yml * Update issue-comment.yml
Co-authored-by: Luka S <github@jaffaketchup.dev>
|
I tested the workflows on my fork, hope I fixed every bug. |
waiting for user responselabel automaticallystaleafter 3 weeks. This is a reminder for the user to answer a question or provide requested information.waiting for user responseandstalelabel gets automatically removed.