3 ms·
I agree with this generally, but I’ll offer a bit of nuance for an edge case: for extremely active repositories with “rolling” changes (i.e., ones where it’s a
by woodruffw 5y ago
I agree with this generally, but I’ll offer a bit of nuance for an edge case: for extremely active repositories with “rolling” changes (i.e., ones where it’s a user error to not be on the latest HEAD), stale bots do a great job of handling the “it broke for me last week, but I haven’t tried any of the changes since” issues that frequently occur.
- IshKebab 5y agoThey do a great job of closing those issues, and also issues that are still valid. Not very useful. The problem is that there's no way to say to stalebot "this issue won't magically be fixed by time, I'm not going to comment here every 3 months to keep it open".