From 69ab7faa6419fd8bc076baf80ee086edc7ca0973 Mon Sep 17 00:00:00 2001
From: anmolnagpal <anmol@clouddrove.com>
Date: Thu, 7 Mar 2024 19:48:28 +0530
Subject: [PATCH 1/3] feat: added templates

---
 .github/PULL_REQUEST_TEMPLATE.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index ec15a22..de726b2 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -19,5 +19,3 @@ describe your code changes in detail for reviewers. Explain the technical soluti
 - [ ] If it is a core feature, I have added thorough tests.
 - [ ] Do we need to implement analytics?
 - [ ] Will this be part of a product update? If yes, please write one phrase about this update.
-
-

From 1fb780355f4edb4527371c061ac9aa77c5d2292a Mon Sep 17 00:00:00 2001
From: anmolnagpal <anmol@clouddrove.com>
Date: Thu, 7 Mar 2024 21:08:51 +0530
Subject: [PATCH 2/3] feat: added templates

---
 .github/PULL_REQUEST_TEMPLATE.md | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index de726b2..5a67dfd 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,17 +1,13 @@
 ## Describe your changes
-
-added pull request template 
+added pull request template
 
 ## Bug description
-
 Clearly and concisely describe the problem. 
 
 ## Issue ticket number and link
-
 there was no issue
 
-## Solution description 
-
+## 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

From db6cba9f4754c2fef8795417b9ffe95e62f772fc Mon Sep 17 00:00:00 2001
From: anmolnagpal <anmol@clouddrove.com>
Date: Wed, 13 Mar 2024 21:19:42 +0530
Subject: [PATCH 3/3] feat: added templates

---
 .github/PULL_REQUEST_TEMPLATE.md | 51 ++++++++++++++++++++++++++++++++
 1 file changed, 51 insertions(+)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 5a67dfd..81d3e9b 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,9 +1,52 @@
+<!--
+     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
 
+## **What type of PR is this? (check all applicable)**
+- [ ] Refactor
+- [ ] Feature
+- [ ] Bug Fix
+- [ ] Optimization
+- [ ] Documentation Update
+
 ## Bug description
 Clearly and concisely describe the problem. 
 
+## Related Tickets & Documents
+
+<!--
+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 #
+
 ## Issue ticket number and link
 there was no issue
 
@@ -15,3 +58,11 @@ describe your code changes in detail for reviewers. Explain the technical soluti
 - [ ] If it is a core feature, I have added thorough tests.
 - [ ] Do we need to implement analytics?
 - [ ] 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