From 937c7e957deff9fae55f2f9ed8532875d1345866 Mon Sep 17 00:00:00 2001
From: psychedelicious <4822129+psychedelicious@users.noreply.github.com>
Date: Thu, 14 Dec 2023 08:35:11 +1100
Subject: [PATCH] add merge plan to PR template

---
 .github/pull_request_template.md | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 02bc10df90..0f0b953be7 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -42,6 +42,21 @@ Please provide steps on how to test changes, any hardware or
 software specifications as well as any other pertinent information. 
 -->
 
+## Merge Plan
+
+<!--
+A merge plan describes how this PR should be handled after it is approved.
+
+Example merge plans:
+- "This PR can be merged when approved"
+- "This must be squash-merged when approved"
+- "DO NOT MERGE - I will rebase and tidy commits before merging"
+- "#dev-chat on discord needs to be advised of this change when it is merged"
+
+A merge plan is particularly important for large PRs or PRs that touch the
+database in any way.
+-->
+
 ## Added/updated tests?
 
 - [ ] Yes