4 ms·

Can always close as WONTFIX - reopen if you have a pull request in the first case ... and just WONTFIX the license changers.

• akerro 10y ago
  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.
  • jbrooksuk 10y ago
    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 https://github.com/Cachethq/Cachet
    • facorreia 10y ago
      Would it help creating a page with "common reasons for closing" and adding a note with a link to that page?
      • akerro 10y ago
        More work to avoid more work?
  • deleted 10y ago
    [deleted]
  • nv-vn 10y ago
    Can't you just lock the thread?
    • RyanCavanaugh 10y ago
      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.
      • adekok 10y ago
        The solution for that is to ban the person.
      • Bahamut 10y ago
        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.