From 129bc896df29ed5cedd915b094365058b19137a1 Mon Sep 17 00:00:00 2001
From: CalMWolfs <94038482+CalMWolfs@users.noreply.github.com>
Date: Mon, 7 Oct 2024 21:08:50 +1100
Subject: Backend: Update pr template (#2687)

---
 pull_request_template.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/pull_request_template.md b/pull_request_template.md
index b004c1c13..dba81f46b 100644
--- a/pull_request_template.md
+++ b/pull_request_template.md
@@ -1,4 +1,6 @@
-<!-- remove all unused parts -->
+<!-- remove all unused parts 
+
+The title of your PR should be descriptive and concise. It should be in the format of `Type: Description`. For example, `Feature: Add new command` or `Fix: Bug in command`. If there are multiple types of changes these can be separated by an ampersand. For example, `Feature & Fix: Add new command and fix bug in command`.
 
 ## PR Reviews
 
@@ -6,6 +8,8 @@ When your PR is marked as ready for review, some of our maintainers will look th
 
 Make sure to only mark your PR as "Ready to review" when it is. If you still want to do major changes, you can keep a draft PR open until then.
 
+-->
+
 ## Dependencies
 - pr_number_or_link_here
 
-- 
cgit