Switch to GitHub issue forms

[litetex]

What is it?

• Bugfix (user facing)
• Feature (user facing)
• Codebase improvement (dev facing)
• Meta improvement to the project (dev facing)

Description of the changes in your PR

This is a first step/try to stop issue spamming by users which are unable to read the template/delete it.
Backstory: We got ~30 issue duplicates in one day despite having a pinned issue (→ #7734)

This switches our issue templates to GitHub issue form(s)-templates (still in beta) which should be more intuitive for users to fill out.

This is also a preparation for #6941

See also

• https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms
• https://github.blog/changelog/2021-06-23-issues-forms-beta-for-public-repositories/

Before/After Screenshots/Screen Record

→ Live demo: https://github.com/litetex/np-gh-issue-forms/issues/new/choose

• Before:

• After:

Due diligence

• I read the contribution guidelines.

[opusforlife2]

Is it okay even if they're still in beta? I know the Matrix/Element teams use them for all their repos.

[opusforlife2]

The dumdum CI shouldn't run when non-code files are modified.

[litetex]

Is it okay even if they're still in beta? I know the Matrix/Element teams use them for all their repos.

I think it works better than the current solution. However I did no long time monitoring so far.
In case of emergency we could also go back to the previous templates.

The dumdum CI shouldn't run when non-code files are modified.

A new issue with the CI label would be appreciated.
Also this could be helpful:

[TheAssassin]

Please feel free to take some inspiration from https://github.com/TheAssassin/AppImageLauncher/tree/master/.github/ISSUE_TEMPLATE. I think you mostly converted the existing template, but there is some potential for improvements. I'll leave a review shortly.

[TheAssassin]

I reviewed one of them now, but most of my feedback applies to all three.

[litetex]

@TheAssassin
Thank you for the feedback.
I reworked the templates accordingly (note that I modified some parts).

[opusforlife2]

I love it. This is so much better than letting users manually fiddle with Markdown.

[litetex]

@opusforlife2
Thank you for the feedback.
I reworked the templates accordingly (note that I modified some parts).

[opusforlife2]

MERGE MERGE MERGE

[litetex]

@mhmdanas
Done

[triallax]

LGTM

_{yay no more issues with incomplete templates}

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[opusforlife2]

Thanks, litetex!