Use issue templates for creating issues

[Emojigit]

This PR uses issue templates to replace the legacy, markdown-only issue form. This forces everyone who want to submit an issue (either bug report or feature request) must follow the formats.

Two notifications are added at the template choose page: one to direct MTG issues to MTG's issue tracker, another to guide issue submitters submitting third-party games issues to search for their issue trackers on CDB.

This PR is Ready for Review. As the main branch of my fork, it can now be tested directly in my fork's create issue page. Click here to pick a template.

I don't know can I create such type of template for PRs or not, but I don't see the need of doing so. We expect PR creators to know how to handle the formats of the markdown description, and should have the freedom of changing it.

[rollerozxa]

Is CPU really necessary for issues? I know it's in the original bug report template but I don't know whether it would affect the reproduction of any issues, as opposed to GPUs that can have very unique graphical issues.

[Emojigit]

Well, we should ask the original author @nerzhul.

[Emojigit]

In my own opinion, I think CPU model is not a must to provide, as microcode bugs are usually not what Minetest Developers can handle. However, providing as much information as possible is always recommended for spotting the problem more accurately.

[Desour]

TBH, I prefer the simple markdown thing we have now.
If someone submits a low quality issue and doesn't even fill out the template, the issue can simply be closed manually.
The reason why I don't like this new template is that it is to rigid:

• Some issues just don't fit exactly into the classic feature request or bug report category. People who open these issues normally know what they're doing.
• You can't delete or add subsections in the issue, right? This makes describing the issue harder.
• The fields in the bug report template are also too rigid. Most issues don't require knowledge about the gpu or cpu model. But they do need other information, for example the relevant settings.

[rubenwardy]

Some issues just don't fit exactly into the classic feature request or bug report category. People who open these issues normally know what they're doing.

You can still open blank issues here:

The fields in the bug report template are also too rigid. Most issues don't require knowledge about the gpu or cpu model. But they do need other information, for example the relevant settings.

Might be worth making the fields higher level and less specific. For example, a single field rather than individual ones for everything

[Emojigit]

Might be worth making the fields higher level and less specific. For example, a single field rather than individual ones for everything

May you specifically point out how the templates can be improved?

[srifqi]

The concept looks good. The implementation has some small issues.

[srifqi]

This PR looks good to me.

[Emojigit]

I've added "Active renderer" and "Irrlicht device" fields into my issue template, hence merging f41e9e3 into my PR.

[rubenwardy]

"Irrlicht device" is a pretty meaningless question, no one is going to be able to answer this. And it's something that's pretty much fixed based on the platform. I'd just remove this for now

[rubenwardy]

This is a duplicate of active renderer

[Emojigit]

Since the PR is already merged, should I create a new PR to remove these?