4 ms·
I honestly detest stalebot - if you don't want to keep on top of your projects' issues/PRs, fine - but don't artificially and automatically close issues that ex
by lol768 5y ago
I honestly detest stalebot - if you don't want to keep on top of your projects' issues/PRs, fine - but don't artificially and automatically close issues that explain very real limitations in your project just because you don't have the time to look at them. If you do that, you rob the next n visitors the ability to understand what works and more importantly what doesn't work at a glance, from the open issues/PRs list.
That security vulnerability or bug isn't going to vanish into the ether because a "helpful" bot closed the issue. It'll still be there - but it'll get lost in every other closed issue.
I will happily just comment on the issue every single time the bot closes it out of spite to force it to be re-opened. Hell, it's probably overdue someone writing an anti-stale-bot that does exactly that.
Related: https://drewdevault.com/2021/10/26/stalebot.html https://drewdevault.com/2021/10/26/stalebot.html
- lostdog 5y agoReally stalebot shouldn't close issues. It should put them into a "stale" state, where they still exist for users to read, but are filtered out when maintainers look at a list of issues with the project.
- geerlingguy 5y agoIf there is a bug, I typically mark it with a `bug` label, and I configured stale bot to ignore those issues, so they do remain open: https://github.com/geerlingguy/ansible-role-docker/blob/master/.github/stale.yml#L15 https://github.com/geerlingguy/ansible-role-docker/blob/mast...
- remram 5y agoIf triage is happening stalebot is fine. Unleash it on "need-more-info" issues, or feature requests with no upvotes, I don't think anyone has a problem with that. I think people are objecting to un-triaged issues being able to go stale, and you then have to keep fighting the bot every month because the maintainer doesn't spend the time to confirm it while demanding you waste your own time to bump it.