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?
-
Adding questions to the issue template can help with getting the reporter to switch into the "How can I help the maintainer reproduce this error?" mode. Keep the questions simple and direct. "What is the command line you used when this error message occurred?"
I guess it would be a good idea to add a pointer to the FAQ in the issue template. Right now the issue template for Yosus is empty I think..
-
-
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.
- Show replies
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.