Create standard templates for issues

[Tbusk]

Description

Rather than start with empty issues, a few types should be created so that:

• People know what info may be helpful
• To reduce the time to create issues
• Have consistent format of issues between parties

Typically, these are common:

• Bug
• Feature
• Change

The way to have a form-like template is to use yml-based templates:

• https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
• https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms

[colinkiama]

Oh yes I’m a fan of these!

[Tbusk]

Oh yes I’m a fan of these!

What fields do you want in these/how do you want them structured? Or if I was to add these, want to customize the final version instead @colinkiama ?

I have three of these setup in my plugin's repo that can be used; probably just need to tweak them a little.

https://github.com/Tbusk/vala-jetbrains-plugin/tree/main/.github/ISSUE_TEMPLATE

[colinkiama]

I have three of these setup in my plugin's repo that can be used; probably just need to tweak them a little.

https://github.com/Tbusk/vala-jetbrains-plugin/tree/main/.github/ISSUE_TEMPLATE

Wow from your repo, I think that feature_request.yml and change_request.yml can be added as-is.

However, with the bug report section, there are some additional fields that should be added like "Browsers affected" and "Node Version".

I should be able to add these in a week from now.

Feel free to make a merge request if you want to do it before then.