feat: added templates

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,17 +1,56 @@
+<!--
+     For Work In Progress Pull Requests, please use the Draft PR feature,
+     see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details.
+
+     For a timely review/response, please avoid force-pushing additional
+     commits if your PR already received reviews or comments.
+
+     Before submitting a Pull Request, please ensure you've done the following:
+     - 📖 Read the Forem Contributing Guide: https://developers.forem.com/contributing-guide/forem#create-a-pull-request
+     - 📖 Read the Forem Code of Conduct: https://github.com/forem/forem/blob/main/CODE_OF_CONDUCT.md
+     - 👷‍♀️ Create small PRs. In most cases this will be possible.
+     - ✅ Provide tests for your changes.
+     - 📝 Use descriptive commit messages.
+     - 📗 Update any related documentation and include any relevant screenshots.
+
+     NOTE: Pull Requests from forked repositories will need to be reviewed by
+     a Forem Team member before any CI builds will run. Once your PR is approved
+     with a `/ci` reply to the PR, it will be allowed to run subsequent builds without
+     manual approval.
+-->
+
+
 ## Describe your changes
+added pull request template
 
-added pull request template 
+## **What type of PR is this? (check all applicable)**
+- [ ] Refactor
+- [ ] Feature
+- [ ] Bug Fix
+- [ ] Optimization
+- [ ] Documentation Update
 
 ## Bug description
-
 Clearly and concisely describe the problem. 
 
-## Issue ticket number and link
+## Related Tickets & Documents
 
-there was no issue
+<!--
+For pull requests that relate or close an issue, please include them
+below.  We like to follow [Github's guidance on linking issues to pull requests](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue).
+
+For example having the text: "closes #1234" would connect the current pull
+request to issue 1234.  And when we merge the pull request, Github will
+automatically close the issue.
+-->
+
+- Related Issue #
+- Closes #
 
-## Solution description 
+## Issue ticket number and link
+there was no issue
 
+## Solution description
 describe your code changes in detail for reviewers. Explain the technical solution you have provided and how it fixes the issue case.
 
 ## Checklist before requesting a review
@@ -21,3 +60,9 @@ describe your code changes in detail for reviewers. Explain the technical soluti
 - [ ] Will this be part of a product update? If yes, please write one phrase about this update.
 
 
+## **Added/updated tests?**
+We encourage you to keep the code coverage percentage at 80% and above.
+
+- [ ] Yes
+- [ ] No, and this is why: please replace this line with details on why tests have not been included
+- [ ] I need help with writing tests