Added a PR template and updated the ISSUE templates.

Author: rfelber

.github/ISSUE_TEMPLATE/bug_report.md

@@ -5,7 +5,7 @@ labels: bug
 
 ---
 <!--
-Thanks for reporting an issue in the documentation 🙌 ❤️
+Thank you for reporting an issue in our project 🙌
 
 Before opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
 -->

.github/ISSUE_TEMPLATE/documentation_issue.md

@@ -5,7 +5,7 @@ labels: documentation
 
 ---
 <!--
-Thanks for reporting an issue in our documentation 🙌 ❤️
+Thank you for reporting an issue in our documentation 🙌
 
 Before opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
 -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,10 +1,10 @@
 ---
-name: "Feature request"
+name: "➹ Feature request"
 about: "Suggest an idea for this project"
 
 ---
 <!--
-Thanks for reporting an issue in our documentation 🙌 ❤️
+Thank you for reporting an issue in our documentation 🙌
 
 Before opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
 -->

.github/ISSUE_TEMPLATE/new_hook.md

@@ -5,7 +5,7 @@ labels: 'hook'
 ---
 
 <!--
-Thanks for contributing to the project 🙌 ❤️
+Thank you for contributing to our project 🙌
 
 Before opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead. Also, please, have a look at our FAQs and existing questions before opening a new question.
 -->
@@ -29,7 +29,7 @@ Before opening a new issue, please make sure that we do not have any duplicates
 Hint: A general guide how to implement a new scanner is documented [here](https://github.com/secureCodeBox/secureCodeBox-v2/tree/master/docs/developer-guide)
 -->
 
-- [ ] Create a new folder with the name of the [scanner here](https://github.com/secureCodeBox/secureCodeBox-v2/tree/master/scanners), based on the existing template
+- [ ] Create a new folder with the name of the [hook here](https://github.com/secureCodeBox/secureCodeBox-v2/tree/master/scanners), based on the existing template
 - [ ] Add a README.md and give a brief overview of the scanner and its configuration options.
 - [ ] Implement a new scanner specific scan-type.yaml
 - [ ] Implement a new scanner specific parse-definition.yaml
@@ -38,4 +38,4 @@ Hint: A general guide how to implement a new scanner is documented [here](https:
 - [ ] Use the parserSDK to implement a new findings parser (currently based on NodeJS)
 - [ ] Add unit tests with at minimum 80% test coverage
 - [ ] Add some example scan.yaml and finding.yaml files in the example folder
-- [ ] Implement a new integration test for the scanner [here](https://github.com/secureCodeBox/secureCodeBox-v2/tree/master/tests/integration)
+- [ ] Implement a new integration test for the hook [here](https://github.com/secureCodeBox/secureCodeBox-v2/tree/master/tests/integration)

.github/ISSUE_TEMPLATE/new_security_scanner.md

@@ -5,7 +5,7 @@ labels: 'scanner'
 ---
 
 <!--
-Thanks for contributing to the project 🙌 ❤️
+Thank you for contributing to our project 🙌
 
 Before opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead. Also, please, have a look at our FAQs and existing questions before opening a new question.
 -->

.github/ISSUE_TEMPLATE/question.md

@@ -5,7 +5,7 @@ labels: question
 
 ---
 <!--
-Thanks for contributing to the project 🙌 ❤️
+Thank you for supporting our project 🙌
 
 Before opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead. Also, please, have a look at our FAQs and existing questions before opening a new question.
 -->

.github/pull_request_template.md

@@ -0,0 +1,20 @@
+<!-- 
+Thank you for your contribution to our Project 🙌 
+
+Before submitting your Pull Request, please take the time to check the points below and provide some descriptive information.
+* [ ] If this PR comes from a fork, please [Allow edits from maintainers](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork)
+* [ ] Set a meaningful title. Format: {task_name} (closes #{issue_number}). For example: Use logger (closes #41)
+* [ ] [Link your Pull Request to an issue](https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue) (if applicable)
+* [ ] Create Draft pull requests if you need clarification or an explicit review before you can continue your work item.
+* [ ] Make sure that your PR is not introducing _unncessary_ reformatting (e.g., introduced by on-save hooks in your IDE)
+* [ ] Make sure each new source file you add has a correct license header.
+-->
+
+## Checklist
+
+* [ ] Test your changes as thoroughly as possible before you commit them. Preferably, automate your test by unit/integration tests.
+* [ ] Make sure `npm test` runs for the whole project.
+
+## Description
+
+<!-- Please be brief in describing which issue is solved by your PR or which enhancement it brings -->