From f701e72e8412b10e0d7d68adfe59584e8262e464 Mon Sep 17 00:00:00 2001
From: Joshua Graber <joshua.d.graber@gmail.com>
Date: Tue, 18 Jun 2024 09:52:13 -0400
Subject: [PATCH] docs(github): add pr template

this commit will also trigger a major release: 2.7.0 should have been 3.0.0

BREAKING CHANGE: trigger major release
---
 .github/pull_request_template.md | 21 +++++++++++++++++++++
 1 file changed, 21 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..82964df
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,21 @@
+<!-- Title of PR should use a standard commit prefix (feat, fix, chore, etc.) followed by an optional context ((components), (linting), etc), and a succinct description. I.E. feat(components): add MyFancyComponent -->
+
+<!-- Does not have to match PR title. I.E. MyFancyComponent -->
+# {Insert short title}
+
+<!-- What is the rationale for the changes? -->
+## Background
+- a
+- b
+- c
+
+<!-- What is the description of the changes? -->
+## Description
+- Adds this
+- Removes that
+
+## Acceptance Criteria
+<!-- What are the steps to test the changes? -->
+1. a
+2. b
+3. c
\ No newline at end of file