I love this, so I

RE: https://aus.social/@projectgus/116451450326279473

This is the single best reason to never ever use a stale bot on your project’s issue tracker.

Apr 23 at 4:58amWeb
Show threadI love this, so IApr 23

If you insist on doing stale issues, because I dunno you work for a company and number of open tickets are your KPI, then you introduce a new tag or status called “more info needed” or something like that, and your metrics exclude tickets with that tag or status. The stale issue bot is the only one allowed to use this tag or status. It is only applied when someone from your project is the last non-bot response. As soon as any non-bot response is received the status or tag is cleared and the timer is reset.

NEVER close a stale issue. If someone put time into creating an issue, they deserve an answer.

Show threadVirtualWolfApr 23
@jpm YEPPPP. Fucking hate those stale issue bots with a passion.
Show threadXCondEApr 23

@jpm I don’t mind closing as “cannot reproduce” or “won’t do”.

They can always reopen it with more info.

Leaving things open that you have no intention of working on sends a conflicting message.

Show threadb4ux1t3 #1️⃣Apr 23

@jpm “hey you proved that this is a problem, and have no more actual information to give because you _already gave everything we needed_, but because you didn’t talk for two weeks we’re going to close this even though it’s an easy win.”

Sigh. And it’s always the big companies who actually have the resources to watch their open source stuff, you know?