Pull request template enhancements (#5)

* Pull request template enhancements

* List of change types for selection

* Wording for checks

* Make change types a list for when there are multiple applicable

* Move away from checklist and back to review reminders, now expanded

* Comment for indicating reviewer guidelines are optional

* Add suggestions and clarify the more severe warnings

* Mention fixed width images

Author: withinfocus

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,28 +1,51 @@
-## Type of change
+## 🎟️ Tracking
 
-<!-- (mark with an `X`) -->
+<!-- Paste the link to the Jira or GitHub issue or otherwise describe / point to where this change is coming from. -->
 
-```
-- [ ] Bug fix
-- [ ] New feature development
-- [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
-- [ ] Build/deploy pipeline (DevOps)
-- [ ] Other
-```
+## 🚧 Type of change
 
-## Objective
+<!-- Choose those applicable and remove the others. -->
 
-<!--Describe what the purpose of this PR is. For example: what bug you're fixing or what new feature you're adding-->
+-   🐛 Bug fix
+-   🚀 New feature development
+-   🧹 Tech debt (refactoring, code cleanup, dependency upgrades, etc.)
+-   🤖 Build/deploy pipeline (DevOps)
+-   🎂 Other
 
-## Code changes
+## 📔 Objective
 
-<!--Explain the changes you've made to each file or major component. This should help the reviewer understand your changes-->
-<!--Also refer to any related changes or PRs in other repositories-->
+<!-- Describe what the purpose of this PR is, for example what bug you're fixing or new feature you're adding. -->
 
--   **file.ext:** Description of what was changed and why
+## 📋 Code changes
 
-## Before you submit
+<!-- Explain the changes you've made to each file or major component. This should help the reviewer understand your changes. -->
+<!-- Also refer to any related changes or PRs in other repositories. -->
 
--   Please add **unit tests** where it makes sense to do so (encouraged but not required)
--   If this change requires a **documentation update** - notify the documentation team
--   If this change has particular **deployment requirements** - notify the DevOps team
+-   **file.ext:** Description of what was changed and why.
+
+## 📸 Screenshots
+
+<!-- Required for any UI changes; delete if not applicable. Use fixed width images for better display. -->
+
+## ⏰ Reminders before review
+
+-   Contributor guidelines followed
+-   All formatters and local linters executed and passed
+-   Written new unit and / or integration tests where applicable
+-   Used internationalization (i18n) for all UI strings
+-   CI builds passed
+-   Communicated to DevOps any deployment requirements
+-   Updated any necessary documentation or informed the documentation team
+
+## 🦮 Reviewer guidelines
+
+<!-- Suggested interactions but feel free to use (or not) as you desire! -->
+
+-   👍 (`:+1:`) or similar for great changes
+-   📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info
+-   ❓ (`:question:`) for questions
+-   🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
+-   🎨 (`:art:`) for suggestions / improvements
+-   ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention
+-   🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt
+-   ⛏ (`:pick:`) for minor or nitpick changes