You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Admittedly I think I originally proposed adding the stale bot to automatically close out issues that users had become non-respondent to, but this was during a time when the ratio of users not replying to issues going unaddressed was a lot higher. Given that the pace of development of the extension has slowed down (that is not meant as a slight at all I am extremely grateful for all the work that is done here!) I am wondering if the bot is doing more harm that good now with actual issues getting closed due to a lack of attention rather than user non-respondence.
I wondering if a pragmatic middle ground would be to make the stale bot manual instead of automatic. E.g. if a developer never gets a response to an issue they can just manually label it as stale to give the user 30 days to respond before it then gets automatically closed?
The text was updated successfully, but these errors were encountered:
Admittedly I think I originally proposed adding the stale bot to automatically close out issues that users had become non-respondent to, but this was during a time when the ratio of users not replying to issues going unaddressed was a lot higher. Given that the pace of development of the extension has slowed down (that is not meant as a slight at all I am extremely grateful for all the work that is done here!) I am wondering if the bot is doing more harm that good now with actual issues getting closed due to a lack of attention rather than user non-respondence.
I wondering if a pragmatic middle ground would be to make the stale bot manual instead of automatic. E.g. if a developer never gets a response to an issue they can just manually label it as stale to give the user 30 days to respond before it then gets automatically closed?
The text was updated successfully, but these errors were encountered: