3 ms·

I mark bugs, security-related issues, and planned features with appropriate labels, and the stale bot ignores those: https://github.com/geerlingguy/ansible-role

I mark bugs, security-related issues, and planned features with appropriate labels, and the stale bot ignores those: https://github.com/geerlingguy/ansible-role-docker/blob/master/.github/stale.yml#L15 https://github.com/geerlingguy/ansible-role-docker/blob/mast... Not all maintainers do the same. And some even _lock issues_, which I hate, because even closed issues can have a very fruitful discussion long after the issue was originally posted.

j1elo 5y ago
Then you are, in my humble opinion, doing it exactly right :-) (apart from going all-in and just never closing anything, but yours is a very good middle ground) > even closed issues can have a very fruitful discussion long after the issue was originally posted 100% agree! In some occasions I've learned a lot from reading long related conversations in a bug report that had been closed or resolved long since.
mkeedlinger 5y ago
TIL that my hatred of stale bot is somewhat misplaced, because it seems that it can be configured in a way I think is a lot more acceptable. Shame when it's set to be aggressive, it can be a serious hindrance. Issues almost act like a user forum, and can be super useful even if the maintainer doesn't want to put energy into that particular issue. I've found some really helpful work-arounds in "stale" issues.