From aca012138155f63a44d98db4b8269863f792f330 Mon Sep 17 00:00:00 2001
From: ValeriaBassi <95831211+ValeriaBassi@users.noreply.github.com>
Date: Thu, 7 Mar 2024 11:15:52 -0300
Subject: [PATCH] Create pull_request_template.md

---
 .github/pull_request_template.md | 54 ++++++++++++++++++++++++++++++++
 1 file changed, 54 insertions(+)
 create mode 100644 .github/pull_request_template.md

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 0000000..1f64c46
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,54 @@
+<!--
+    PR Title Format: <type>(<github-issue>): <subject>
+
+    Type must be one of the following:
+
+    * build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
+    * ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
+    * docs: Documentation only changes
+    * feat: A new feature
+    * fix: A bug fix
+    * perf: A code change that improves performance
+    * refactor: A code change that neither fixes a bug nor adds a feature
+    * style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
+    * test: Adding missing tests or correcting existing tests
+
+    Squash Merge
+    The criteria described above will be checked in the PR title which is the default commit message when performing a squash merge.
+    **DO NOT MODIFY** this message as it is used by the release tool to generate proper semantic versioning.
+-->
+
+### 📜 Description
+
+<!--
+    Describe your changes in detail.
+    Mainly answer the "What" and "How". What is the PR changing? What is it adding/modifying/removing? What will the new behavior be?
+    How is the change introduced?
+    In addition, you can also comment on your own PR using "Add single comment".
+-->
+
+
+### 🧪 Accept Criteria Tests
+
+<!--
+    Describe the manual tests that you ran to verify your changes.
+    Provide instructions so we can reproduce.
+    Also list any relevant details for your test configuration.
+    Add before/after screenshots and video recordings if relevant (UI change, user flow, etc.).
+-->
+
+### 🔮 Last Notes
+
+<!--
+    What are the next steps to complete this piece of work? Any cleanup? TODO? Improvements? etc.
+-->
+
+### 📋 Author Checklist
+- [ ] Review my on PR.
+
+### 📋Reviewer Checklist
+
+- [ ] There is no hardcoding in the code.
+- [ ] The tests cover various aspects of functionality.
+- [ ] There is no **any** type in the code.
+- [ ] The target branch is **main**.