From db1e6c1d00c4c271dee811cfd592f54d6ffcde29 Mon Sep 17 00:00:00 2001
From: jwhitak <69739118+jwhitak@users.noreply.github.com>
Date: Sat, 4 May 2024 21:39:57 -0500
Subject: [PATCH] WIP pull request template changes

---
 .github/PULL_REQUEST_TEMPLATE.md | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 0e08558bc5be..f95004b221cd 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,15 +1,22 @@
 <!--
 Pull requests must be atomic. Change one set of related things at a time.
 Test your changes. PRs that were not tested will not be accepted.
+Not including sections of the template may result in having your PR closed.
 
-You can self-label your PR. See https://ss13.moe/wiki/index.php/Guide_to_Writing_a_Pull_Request -->
+You can self-label your PR. See https://ss13.moe/wiki/index.php/Guide_to_Writing_a_Pull_Request
+Common labels include bugfix, content, tweak, and balance. Enclose them in [ square brackets. -->
+
+<!-- You can post a header, sample images, and/or simple description here for a quick summary. -->
 
 ## What this does
 <!-- Describe here all changes included in the PR. -->
 <!-- If the PR addresses existing issues, here is where you would write "Closes #99999". See https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue -->
 
 ## Why it's good
-<!-- Explain why you think these changes are good. -->
+<!-- Explain why you think these changes are good, or otherwise why you wanted to make them and have them merged. -->
+
+## How it was tested
+<!-- Document what procedures you used to test this PR here, including any images if helpful. -->
 
 ## Changelog
 <!-- See https://ss13.moe/wiki/index.php/Guide_to_Writing_a_Pull_Request -->