-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stalebot considered harmful #543
Comments
My +1 on that, dear sir @hholst80. And to add insult to injury: beware of probot/stale#312. I've seen it time and time again. Most recently, in #445 — the bot used to obey and removed the That nobody is fixing neither "metoo"-ing an issue that describes a defect — doesn't mean the defect went away. It means that people who use the software went away. |
Somehow it took 15 days rather than a week... still, as predicted, it ignored my command. @stalebot is a rogue bot — violates Asimov's Second Law of Robotics. Where's that robot prison, how do I call the robot police?.. |
🎉 This issue has been resolved in version 1.6.9 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Maybe I am wrong? Maybe I am right? I just ask that you consider before adding automation, not just adding "automation" just because it is possible add it. Add automation bots when it does make sense, when it replaces human labor. Why would anyone run around all issues marking them "Stale"? Stalebot is a solution to a problem we don't have. There are currently 10 open issues in this repo. I think we can navigate them without the assistance of Mr. Stalebot.
The text was updated successfully, but these errors were encountered: