stale

And old rant in their issue queue: https://github.com/probot/stale/pull/107#issuecomment-379021... > Thesis: Stalebot -- in dutiful service of current human resource constraints -- feels like it unthinkingly prioritizes discard of past contributors' time resources, over the mobilization of new human resources. I've had a beef with Stale since early on. It's a very old-world view of solving the problem of open source capacity. A better tool would instead try to find and encourage new resources (new contributors), whereas stalebot drives them away, and so kinda cuts the project off at the knees imho, in the short-term, it rescues the cognitive and emotional resources of current contributors, but (in the long-term) drives future contributors away through promoting lack of care and by encouraging maintainers to not interact with them.

Our stale bot doesn't lock issues, merely marks them as closed after a configurable notification time, and a configurable no-activity time. Which stale bot is the author referring to? This stale bot (THE stale bot?) https://github.com/probot/stale, doesn't even have an option to lock the issue.