Create PR template PULL_REQUEST_TEMPLATE.md

[gitressa]

The Issue

• Fixes Add PR template, with Fixes ISSUE link #6038

How This PR Solves The Issue

Adds a PR template file.

[weitzman]

This doesnt add much useful over a plan description box. We dont want to encourage the filing of useless issues that bifurcate the conversation.

[gitressa]

I agree that it should not be required to create a corresponding issue for a PR, PR's should be allowed to stand alone. Drush users linking PR's with issues is a common thing though, if you look under the PR's.

I updated the patch in my branch, to clarify that corresponding a issue to a PR is not required, but it's not getting transferred to this PR, so here it is:

---

name: Pull request
about: For support requests, please use Drupal Answers instead. See https://drupal.stackexchange.com/questions/tagged/drush

Optional: Link pull request and issue, if an issue exists
Drush pull requests don't require an issue, but if an issue exists, you can connect this PR and the issue:

• Fixes #

Describe the pull request
A clear and concise description of what the pull request does, for example which problem it solves, or feature it adds.

Additional information
Add any other context about the pull request here.

[gitressa]

Here are a few PR's, where Drush contributors linked a PR with an issue:

• Replace usage of Assertion\Handle::register() #5852
• Prevent drush from crushing, when command extends non-existent class #5861
• Fix site install command broken in D11 #5883
• GH-5890: fix UpdateRegistry constructor #5891
• Update SiteInstallCommands for interactive install #5895
• Update to symfony7 #5951
• Error with asciinema install on ddev start #5988
• Allow compatability with drush <= 12. See drupal.org/i/3445590. #6019

[weitzman]

If there is an issue, of course it makes sense to link it. I dont think we need to tell people about that authoring features like issue linking, just like we dont tell people about markdown and mentioning people.

[gitressa]

All right.