Hacker News Reader

the norms of issue trackers are strongly opposed to “bump”. these autoclose bots may yet change that

Yes, now the poster of the issue just needs to (tell claude to) write a bot which posts a "bump" comment every 17 days, and the bots will cancel each other out.

In this case there is a two phase staleness check. The bot marks it as stale and it is correct to "bump" it if you think it is still important. The nixpkgs repo works the same way. I think it backs off from adding stale again as it gets bumped.

I'm not saying it's a perfect solution but for projects that deal with large amounts of issues it's workable.

They should just utilize the old joke about hiring: immediately throw away half the tickets, because you don't want to work on an unlucky ticket.

It'd save the run around and have the same ultimate effect. Or, we could properly work on tickets instead of making the gate "has enough time to follow up on this 14 days later"

Reply on news.ycombinator.com