3 ms·
A previous thread on an article about stale bots: https://news.ycombinator.com/item?id=25821092 https://news.ycombinator.com/item?id=25821092 Closing issues au
by chrismorgan 5y ago
A previous thread on an article about stale bots: https://news.ycombinator.com/item?id=25821092 https://news.ycombinator.com/item?id=25821092
Closing issues automatically is bad enough—I’ve long complained about the stale bot, seeking for it to be discontinued with prejudice as it’s only harmful, literally never helpful (as an issue tracker, that is—it may possibly help maintainers’ mental state because it can facilitate more effective ostrich imitation than just ignoring the issues as they pile up).
Then there’s the GitHub action that has largely supplanted it (and which is what’s actually in the screenshot), which doesn’t just close, but locks (no idea if it’s configurable). A bot to close issues I can understand, people have been copying this misfeature from other sorts of trackers (… where it’s also normally a misfeature) for a long time. But making it lock issues is an even stupider idea than closing, amplifying the problems of closing even further for no reason that I can imagine, and I am baffled that that ever got implemented at all. I think it’s indefensible, but I’m rather curious to hear a defence of it.
- oauea 5y agoThe best part is when the developers then close & lock your new issues as duplicates. No discussion allowed, I guess.
- nyuszika7h 5y agoI agree, this is incredibly frustrating. Sometimes it's hard enough to even get developers to reopen issues closed for inactivity, if they're locked it's even worse. I often don't even bother trying to open a new issue for the same thing unless it's critical, I just leave in frustration.