From fca4e52c691719dd2a2a168ee168b07d6b184649 Mon Sep 17 00:00:00 2001
From: Jordan Schmidt <34913460+jordan-n-schmidt@users.noreply.github.com>
Date: Wed, 16 Oct 2024 13:26:02 +0100
Subject: [PATCH] chore: Create PULL_REQUEST_TEMPLATE.md (#311)

---
 .github/PULL_REQUEST_TEMPLATE.md | 17 +++++++++++++++++
 1 file changed, 17 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..680c534
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,17 @@
+# Situation
+<!-- Describe the background or context leading to this change. Include why this work is needed (e.g., a specific problem, user need, or opportunity). What is the current state or issue that prompted this PR? -->
+
+# Task
+<!-- Explain the goal or objective of this change. What specifically needs to be achieved to resolve the situation? Clearly define the scope of the task at hand. -->
+
+# Action
+<!-- Summarize the key steps or decisions taken to accomplish the task. Include what changes were made in the codebase, architecture, or process. What actions were implemented to address the task? -->
+
+# Testing
+<!-- Describe the testing strategy or approach used to validate the changes. Include any relevant test cases, scenarios, or data used to verify the work. How was the work tested? -->
+
+# Results
+<!-- Detail the outcomes of the actions. What improvements or changes have been achieved? Include performance gains, bug fixes, or other tangible outcomes. How will you measure or verify success? -->
+
+# Notes
+<!-- Add any additional context or information. This could include things like links to documentation, related issues, related PRs, follow-up tasks, edge cases considered, or potential risks. Any relevant thoughts or clarifications can go here. -->