Improve PR Templates

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,34 @@
+---
+name: |
+  🐞 Failing Test
+  🐞 Bug Fix
+  ⚙ Improvement
+  🎉 New Feature
+about: You found a bug, have a failing test, want to improve something or add a new feature
+labels: bug or enhancement
+---
+
+## A Pull Request should be associated with an Issue.
+
+> We wish to have discussions in Issues. A single issue may be targeted by multiple PRs.
+> If you're offering a new feature or fixing anything, we'd like to know beforehand in Issues,
+> and potentially we'll be able to point development in a particular direction.
+
+Related issue: 
+
+> Further notes in [Contribution Guidelines](.github/CONTRIBUTING.md)
+> Thank you! We are open to PRs, but please understand if for technical reasons we are unable to accept each and any PR
+
+### Description
+
+This PR [briefly explain what it does]
+
+> In case this PR introduced TypeScript/JavaScript code changes:
+
+- [ ] I have written test cases for the changes in this pull request
+- [ ] I have run `npm run format` before the commit.
+- [ ] `npm test` returns with no unit test errors.
+
+<!--
+- Please target the develop branch when submitting the pull request.
+-->

.github/PULL_REQUEST_TEMPLATE/FAILING_TEST.md

@@ -4,6 +4,27 @@ about: You found a bug and have a failing test?
 labels: bug
 ---
 
+## A Pull Request should be associated with an Issue.
+
+> We wish to have discussions in Issues. A single issue may be targeted by multiple PRs.
+> If you're offering a new feature or fixing anything, we'd like to know beforehand in Issues,
+> and potentially we'll be able to point development in a particular direction.
+
+Related issue: 
+
+> Further notes in [Contribution Guidelines](.github/CONTRIBUTING.md)
+> Thank you! We are open to PRs, but please understand if for technical reasons we are unable to accept each and any PR
+
+### Description
+
+This PR [briefly explain what it does]
+
+> In case this PR introduced TypeScript/JavaScript code changes:
+
+- [ ] I have written test cases for the changes in this pull request
+- [ ] I have run `npm run format` before the commit.
+- [ ] `npm test` returns with no unit test errors.
+
 <!--
 - Please target the develop branch when submitting the pull request.
 -->

.github/PULL_REQUEST_TEMPLATE/FIX.md

@@ -4,6 +4,27 @@ about: You have a fix for a bug?
 labels: bug
 ---
 
+## A Pull Request should be associated with an Issue.
+
+> We wish to have discussions in Issues. A single issue may be targeted by multiple PRs.
+> If you're offering a new feature or fixing anything, we'd like to know beforehand in Issues,
+> and potentially we'll be able to point development in a particular direction.
+
+Related issue: 
+
+> Further notes in [Contribution Guidelines](.github/CONTRIBUTING.md)
+> Thank you! We are open to PRs, but please understand if for technical reasons we are unable to accept each and any PR
+
+### Description
+
+This PR [briefly explain what it does]
+
+> In case this PR introduced TypeScript/JavaScript code changes:
+
+- [ ] I have written test cases for the changes in this pull request
+- [ ] I have run `npm run format` before the commit.
+- [ ] `npm test` returns with no unit test errors.
+
 <!--
 - Please target the develop branch when submitting the pull request.
 -->

.github/PULL_REQUEST_TEMPLATE/IMPROVEMENT.md

@@ -4,6 +4,27 @@ about: You have some improvement to make setup-php better?
 labels: enhancement
 ---
 
+## A Pull Request should be associated with an Issue.
+
+> We wish to have discussions in Issues. A single issue may be targeted by multiple PRs.
+> If you're offering a new feature or fixing anything, we'd like to know beforehand in Issues,
+> and potentially we'll be able to point development in a particular direction.
+
+Related issue: 
+
+> Further notes in [Contribution Guidelines](.github/CONTRIBUTING.md)
+> Thank you! We are open to PRs, but please understand if for technical reasons we are unable to accept each and any PR
+
+### Description
+
+This PR [briefly explain what it does]
+
+> In case this PR introduced TypeScript/JavaScript code changes:
+
+- [ ] I have written test cases for the changes in this pull request
+- [ ] I have run `npm run format` before the commit.
+- [ ] `npm test` returns with no unit test errors.
+
 <!--
 - Please target the develop branch when submitting the pull request.
 -->

.github/PULL_REQUEST_TEMPLATE/NEW_FEATURE.md

@@ -4,6 +4,27 @@ about: You have implemented some neat idea that you want to make part of setup-p
 labels: enhancement
 ---
 
+## A Pull Request should be associated with an Issue.
+
+> We wish to have discussions in Issues. A single issue may be targeted by multiple PRs.
+> If you're offering a new feature or fixing anything, we'd like to know beforehand in Issues,
+> and potentially we'll be able to point development in a particular direction.
+
+Related issue: 
+
+> Further notes in [Contribution Guidelines](.github/CONTRIBUTING.md)
+> Thank you! We are open to PRs, but please understand if for technical reasons we are unable to accept each and any PR
+
+### Description
+
+This PR [briefly explain what it does]
+
+> In case this PR introduced TypeScript/JavaScript code changes:
+
+- [ ] I have written test cases for the changes in this pull request
+- [ ] I have run `npm run format` before the commit.
+- [ ] `npm test` returns with no unit test errors.
+
 <!--
 - Please target the develop branch when submitting the pull request.
 -->