Update: auto-closer warn before closing the issue about eslint-github-bot HOT 3 CLOSED

That would really complicate the logic, and I think kind of defeats the purpose. The point of the auto-closer is to close issues that have shown no activity. If you prompt activity by warning people, the metric gets cloudy and you don't know if any activity occurring is organic or just a "bump" to make sure it doesn't get closed.

On the technical side, it complicates the logic dramatically, because the bot comment counts as activity, so we'd need to loop through comments to check and see if any are from the bot to really figure out if there's any activity.

So I'm 👎 for both reasons.

from eslint-github-bot.

To give some more context around what prompted this idea: I’ve been noticing a non-trivial number of bug reports that get auto-closed without any response from the team. Since they might be valid bug reports that still need to be evaluated, those issues then get reopened with an apology, which can make the process feel hostile to the issue author.

I think we might also be able to solve this at a process level by ensuring we actively triage issues and respond to any issues we remove the triage label from.

I think your points are fair and this might not be a targeted enough approach to solve this. I’m going to close this and continue thinking about it.

from eslint-github-bot.

For reference, a popular GitHub App "stale" bot warns inactive issues before closing.

from eslint-github-bot.