I have not the slightest idea what people expect when they open a github issue with a bunch of copy&pasted error messages, but not the input that produced those errors. How can they not realize that they are just wasting the time of everyone involved?
-
I don't think a link to the FAQ is going to help most of the time. Put the questions you as a maintainer care about directly in the template. That makes it just that little bit harder to ignore, thus slightly more likely to succeed.
But that's the wrong approach. It is *not* about a fixed list of questions. It's about providing the *relevant* information for reproducing the problem without reading the OPs mind. Everyone with a theory of mind should be able to do that.
-
-
Providing a list of question will just result in people mindlessly trying to answer questions but ultimately fail to provide the information necessary for reproducing the issue.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Providing *relevant* information is hard. Use questions to lead a person through the process of reproducing the problem can help. Another useful question is "What did you think this _should_ have done?" but the answer is often "worked" - guess we need something better.
- End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.