Chore: Add configuration wrapper markdown for the bug report template

[revolter]

What is the purpose of this pull request? (put an "X" next to item)

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[x] Other, please explain:

What changes did you make? (Give an overview)

Copied the wrapper markdown from https://github.com/eslint/eslint/blob/master/.github/ISSUE_TEMPLATE.md.

Is there anything you'd like reviewers to focus on?

[aladdin-add]

the change looks good to me. But I'm not sure if the template is still needed.

[revolter]

What do you mean by "needed"? It's currently linked from https://github.com/eslint/eslint/blob/master/.github/PULL_REQUEST_TEMPLATE.md (Bug fix).

[aladdin-add]

we can change the link to .github/ISSUE_TEMPLATE/BUG_REPORT.md, and then remove the identical template. (if it was not used somewhere else)

[platinumazure]

LGTM, thanks!

[revolter]

@aladdin-add, Could be, as I think it's identical, but it's not a decision I can take. I could, instead, close this and open another one that does the removal if you guys decide it's the way to go.

[aladdin-add]

@platinumazure thoughts on #10669 (comment) ?

I'm seeing a rationality to remove the identical template!

[platinumazure]

I'm okay with removing the duplicate template if it won't change the user experience on a different menu. For example, our New Issue link shows 4(?) different options which link to specific templates- not sure if all of those have to be in the same folder. And then we have the default template, and I don't know if that's used elsewhere.

My suggestion would be to create a test repository with the same template setup as our current one, and then make the same change there and see what happens. (Be sure to check on mobile as well, and on tools like GitHub for Windows if they support the use of these templates.) If we see no issues on the test repository, then we can roll it out there. Sound good?

[not-an-aardvark]

• Before GitHub supported multiple issue templates, we had a single issue template with several links to other templates, with the expectation that the user would copy-paste the contents of one of the other templates into the issue. These other templates were in the templates/ folder.
• Now that GitHub supports multiple issue templates, we moved our templates into .github/ISSUE_TEMPLATE/, and we no longer ask users to copy-paste templates into issues. (We still ask users to do this for PRs.)
• I don't think GitHub's UI uses anything in the templates/ folder. It only uses things in the project root or in .github/.
• We could remove the issue template from templates if we update the link in the PR template to point to the templates in .github/ISSUE_TEMPLATE. However, it's worth noting that the files in .github/ISSUE_TEMPLATE have some metadata at the top. I'm not sure if this would degrade the user experience when copy-pasting them.

[platinumazure]

@aladdin-add @not-an-aardvark I'm not clear what the next steps are here. Can this be merged as is, or are changes needed?

[not-an-aardvark]

LGTM, thanks!

[not-an-aardvark]

@platinumazure This can be merged as-is. It might be a good idea for us to consider removing this file from templates/ entirely, but as-is this is an improvement over the existing situation.

[platinumazure]

Merged. Thanks @revolter for contributing!

[revolter]

Thanks for merging!