Add ISSUE_TEMPLATE for github

[fendor]

The purpose would be to reduce the amount of back and forths we usually ask before we can properly answer a question.
It might be overkill to ask that much information.

[Kleidukos]

Pretty sure we could have a tool that would produce a report for some of those values.

* Version of haskell-language-server
* Version of cabal
* Version of ghc
* Version of stack

These ones are fairly easy to automatically get.

[fendor]

Indeed, we could incorporate some of these into haskell-language-server themselves.
Maybe we should also mention haskell-language-server-wrapper as well?

[fendor]

Would we re-invent the wheel if we add something like a --probe-tools command for hls?

[lukel97]

Probably the most sensible thing to do would just be to print the versions/which tools are installed to stderr when haskell-language-server[-wrapper] is run

[fendor]

@bubba I am preparing a patch.

[Ailrun]

LGTM :)

[fendor]

Maybe we should mention that this cli flag is not available in the latest release? Or wait till the next release?

[Ailrun]

I think even after we release the next version, this template should mention the version range in which this command is available. If not, some users will try to run those command with outdated HLS, and then may think this issue template is outdated (or somewhat broken) hence ignore the template.

[alanz]

My only concern is that we will not have issues reported, because people will take a look at the huge amount of info we ask for, and run.

Maybe we should say that the part from Steps to reproduce onward should be filled in if possible? It is not always easy / possible to reproduce an issue, especially if it in on a private code base.

[fendor]

@alanz While I kind of agree, we also need that kind of information if there are bugs. Even on a private code-base, we can not help or debug at all, if not at least big parts of these informations are given. However, I agree that we can make it more clear that most of it is optional and that we dont close issues just because they dont follow that template.

[alanz]

@fendor I agree, but I think raising the issue, and giving the environment can be useful in some cases. And perhaps we should say that if they can repro do that, but if not still report.

Some bugs are straightforward to fix, without the repro, no need to put people through that pain if it is not needed.

[fendor]

Small adaptations to make it clear that the information asked for is optional and may be omitted.
@alanz Is that better, or should we add more clarifications?