From 04aa97f0fd67b2e4298eb8c950d2e62c3454baa6 Mon Sep 17 00:00:00 2001
From: psychedelicious <4822129+psychedelicious@users.noreply.github.com>
Date: Thu, 14 Mar 2024 17:18:54 +1100
Subject: [PATCH] gh: update pr template

---
 .github/pull_request_template.md | 67 +++++++-------------------------
 1 file changed, 13 insertions(+), 54 deletions(-)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 0f0b953be7..3f46dd6161 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,66 +1,25 @@
-## What type of PR is this? (check all applicable)
+<!--Thanks for contributing!-->
 
-- [ ] Refactor
-- [ ] Feature
-- [ ] Bug Fix
-- [ ] Optimization
-- [ ] Documentation Update
-- [ ] Community Node Submission
+## Summary
 
+<!--A description of the changes in this PR. Include the kind of change (fix, feature, docs, etc), the "why" and the "how". Screenshots or videos are useful for frontend changes.-->
 
-## Have you discussed this change with the InvokeAI team?
-- [ ] Yes
-- [ ] No, because:
+## Related Issues / Discussions
 
-      
-## Have you updated all relevant documentation?
-- [ ] Yes
-- [ ] No
+<!--List any related issues or discussions on github or discord. If this PR closes an issue, please use the "Closes #1234" format, so that the issue will be automatically closed when the PR merges.-->
 
+## QA Instructions
 
-## Description
-
-
-## Related Tickets & Documents
-
-<!--
-For pull requests that relate or close an issue, please include them
-below. 
-
-For example having the text: "closes #1234" would connect the current pull
-request to issue 1234.  And when we merge the pull request, Github will
-automatically close the issue.
--->
-
-- Related Issue #
-- Closes #
-
-## QA Instructions, Screenshots, Recordings
-
-<!-- 
-Please provide steps on how to test changes, any hardware or 
-software specifications as well as any other pertinent information. 
--->
+<!--WHEN APPLICABLE: Describe how we can test the changes in this PR.-->
 
 ## Merge Plan
 
-<!--
-A merge plan describes how this PR should be handled after it is approved.
+<!--WHEN APPLICABLE: Large PRs, or PRs that touch sensitive things like DB schemas, may need some care when merging. For example, a careful rebase by the change author, timing to not interfere with a pending release, or a message to contributors on discord after merging.-->
 
-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"
+## Checklist
 
-A merge plan is particularly important for large PRs or PRs that touch the
-database in any way.
--->
+<!--If any of these are not completed or not applicable to the change, please add a note.-->
 
-## Added/updated tests?
-
-- [ ] Yes
-- [ ] No : _please replace this line with details on why tests
-      have not been included_
-
-## [optional] Are there any post deployment tasks we need to perform?
+- [ ] The PR has a short but descriptive title
+- [ ] Tests added / updated
+- [ ] Documentation added / updated