Hacker News Reader

Did it once. Closed an issue I couldn't reproduce and author didn't want to show me their code. I got blamed for not helping them and not fixing problems in my code :) I stopped responding to such issues at all.

View on HN

I maintain Cachet [1] which has 4.4k stars on it. I've closed several issues in a similar vein, only to be ranted at for not giving a reason. I shouldn't have to explain the same reason for the fifth time when you could've searched for it already — but hey, I appreciate the thoughts.

[1] https://github.com/Cachethq/Cachet

Would it help creating a page with "common reasons for closing" and adding a note with a link to that page?

More work to avoid more work?

Can't you just lock the thread?

My experience, having locked a thread exactly once after triaging several thousand reports on TypeScript, is that you immediately get another bug from the same person complaining about how dare you lock an issue.

I've gotten that a few times too - sometimes the issue opener turns out to have been right.

I think more people need to do better at communicating better is what it comes down to.

The solution for that is to ban the person.

Reply on news.ycombinator.com