From b192744d160fa76e26175e9ba6dd52d8788b0632 Mon Sep 17 00:00:00 2001
From: Nathan Tarbert <66887028+NathanTarbert@users.noreply.github.com>
Date: Thu, 21 Sep 2023 09:59:46 -0400
Subject: [PATCH] Create PULL_REQUEST_TEMPLATE.md

---
 profile/PULL_REQUEST_TEMPLATE.md | 76 ++++++++++++++++++++++++++++++++
 1 file changed, 76 insertions(+)
 create mode 100644 profile/PULL_REQUEST_TEMPLATE.md

diff --git a/profile/PULL_REQUEST_TEMPLATE.md b/profile/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 0000000..7ccab29
--- /dev/null
+++ b/profile/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,76 @@
+<!--
+     This Template is inspired by (https://github.com/forem/forem/edit/main/.github/PULL_REQUEST_TEMPLATE.md)  
+     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.
+
+     ## 🧑‍💻 Before submitting a Pull Request, please ensure you've done the following:
+
+- 📖 [Read the DefiKids Contributing Guide:](https://github.com/defikids/.github/blob/main/profile/CONTRIBUTING.md)
+- 📖 [Read the DefiKids Code of Conduct:](https://github.com/defikids/.github/blob/main/CODE_OF_CONDUCT.md)
+- 👷‍♀️ Create 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 DefiKids 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.
+-->
+
+## 😎 What type of PR is this? (check all applicable)
+
+- [ ] Refactor
+- [ ] Feature
+- [ ] Bug Fix
+- [ ] Optimization
+- [ ] Documentation Update
+
+## Description
+_Please replace this line with the description of your PR_
+As noted in the [CONTRIBUTING GUIDE](https://github.com/defikids/.github/blob/main/profile/CONTRIBUTING.md#code-of-conduct)
+
+Pull Requests descriptions must start with 1 of 4 emojis listed here (⭐ | 🌟 | ✨ | 🤩) You choose because we think contributing to open source is fun :)
+
+## Related Issues
+
+<!--
+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 #
+
+## QA Instructions, Screenshots, Recordings
+
+_Please replace this line with instructions on how to test your changes, a note
+on the devices and browsers this has been tested on, as well as any relevant
+images for UI changes._
+
+### UI accessibility checklist
+_If your PR includes UI changes, please utilize this checklist:_
+- [ ] Semantic HTML implemented?
+- [ ] Keyboard operability supported?
+- [ ] Checked with [axe DevTools](https://www.deque.com/axe/) and addressed `Critical` and `Serious` issues.
+- [ ] Color contrast tested?
+
+## 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
+
+## [optional] Are there any post deployment tasks we need to perform?
+
+## [optional] What GIF best describes this PR? Let's make this fun! 
+We like to use the [GIFs for GitHub](https://chrome.google.com/webstore/detail/gifs-for-github/dkgjnpbipbdaoaadbdhpiokaemhlphep/related?hl=en) chrome extension. 
+Just replace this GIF with your own. 
+![lets-do-this](https://github.com/defikids/.github/assets/66887028/217d47a6-d2ef-410f-a96d-b4a256970125)
+