Chore: Add support for new issue experience (fixes #3646)

[guywillis]

Fixes #3646

Chore

• Add new issue_template.md file with YAML frontmatter
• Add new config.yml file to disable blank template

[cahirodoherty-learningpool]

👀

[swashbuck]

👍

[swashbuck]

@guywillis Are you going to include the pull request templates as part of this PR?

[guywillis]

@swashbuck I hadn't planned to as it's not part of the 'new issue experience' feature at present but I can certainly see the benefit of implementing it in advance alongside this work.

From reading https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository it doesn't appear as though pull request templates have been implemented in quite the same way as issue templates. In that:

To create multiple pull request templates and use the template query parameter to specify a template to fill the pull request body, type .github/PULL_REQUEST_TEMPLATE/, then the name of your pull request template. For example, .github/PULL_REQUEST_TEMPLATE/pull_request_template.md. You can also store multiple pull request templates in a PULL_REQUEST_TEMPLATE subdirectory within the root or docs/ directories. For more information, see Using query parameters to create a pull request.

The more information link states that:

https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&template=issue_template.md creates a pull request with a template in the pull request body. The template query parameter works with templates stored in a PULL_REQUEST_TEMPLATE subdirectory within the root, docs/ or .github/ directory in a repository.

The PR template is automatically pulled into the PR when the template file lives in .github/pull_request_template.md. A PR template that lives in .github/PULL_REQUEST_TEMPLATE/pull_request_template.md has to be manually navigated to via the URL in order to populate the PR with the template information.

I concluded that requiring users to amend the URL to use a template when creating a pull request was a step too far at this stage. With that being said, if GitHub implements the PR template in the same fashion as the 'new issue experience' template then it would be beneficial to get that included at this stage.