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
Stale bot is becoming a plague, closing important issues and harming the community. It encourages people to spam issues to keep them open. It ignores much of the issue metadata, like reactions and links to external repositories.
The solution
Eventually I think the issue bot would be nice if it was based on a scoring model. A good first step though would be to prevent closing an issue with a certain number of comments, upvotes (reactions on the root) or external links from other repositories to that issue. If these were filters that could be applied, I think it would accomplish its goal of lowering issues while keeping relative ones still active.
Maybe allowing people to override the bot via community feedback through the comments would also help. Something other than lets blindly close an issue that hasn't been commented on in the last 30 days.
The text was updated successfully, but these errors were encountered:
ashtonian
changed the title
Scoring Issue Activity on things other than comments ie upvotes, links ect..
Scoring Issue Activity on things other than most recent comment ie upvotes, links ect..
Nov 15, 2021
ashtonian
changed the title
Scoring Issue Activity on things other than most recent comment ie upvotes, links ect..
Scoring issue activity on things other than most recent comment ie upvotes, links ect..
Nov 15, 2021
The problem
Stale bot is becoming a plague, closing important issues and harming the community. It encourages people to spam issues to keep them open. It ignores much of the issue metadata, like reactions and links to external repositories.
The solution
Eventually I think the issue bot would be nice if it was based on a scoring model. A good first step though would be to prevent closing an issue with a certain number of comments, upvotes (reactions on the root) or external links from other repositories to that issue. If these were filters that could be applied, I think it would accomplish its goal of lowering issues while keeping relative ones still active.
Maybe allowing people to override the bot via community feedback through the comments would also help. Something other than lets blindly close an issue that hasn't been commented on in the last 30 days.
The text was updated successfully, but these errors were encountered: