⅄ trunk → 25-11-05-difftool

Author: mitchellwrosen

.github/pull_request_template.md

@@ -1,16 +1,14 @@
-**Choose your PR title well:** Your pull request title is what's used to create release notes, so please make it descriptive of the change itself, which may be different from the initial motivation to make the change.
-
 ## Overview
 
-What does this change accomplish and why?
-i.e. How does it change the user experience?
-i.e. What was the old behavior/API and what is the new behavior/API?
+- [ ] What does this change accomplish and why?
+  - [ ] i.e. How does it change the user experience?
+  - [ ] i.e. What was the old behavior/API and what is the new behavior/API?
 
-Feel free to include "before and after" examples if appropriate. (You can copy/paste screenshots directly into this editor.)
+- [ ] Include "before and after" examples if appropriate. (You can copy/paste screenshots directly into this editor.)
 
-If relevant, which Github issues does it close? (See [closing-issues-using-keywords](https://help.github.com/en/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords).)
+- [ ] List any Github issues that this PR closes, in [closing-issues-using-keywords](https://help.github.com/en/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords) format.
 
-## Implementation notes
+## Implementation approach and notes
 
 How does it accomplish it, in broad strokes? i.e. How does it change the Haskell codebase?
 
@@ -21,12 +19,18 @@ What could have been done differently, but wasn't? And why?
 
 ## Test coverage
 
-Have you included tests (which could be a transcript) for this change, or is it somehow covered by existing tests?
+- [ ] Have you included tests (which could be a transcript) for this change, or is it somehow covered by existing tests?
 
-Would you recommend improving the test coverage (either as part of this PR or as a separate issue) or do you think it’s adequate?
+- [ ] Would you recommend improving the test coverage (either as part of this PR or as a separate issue) or do you think it’s adequate?
 
-If you only tested by hand, because that's all that's practical to do for this change, mention that.
+- [ ] If you only tested by hand, because that's all that's practical to do for this change, mention that. Include screenshots.
 
 ## Loose ends
 
 Link to related issues that address things you didn't get to. Stuff you encountered on the way and decided not to include in this PR.
+
+## Final checklist
+
+- [ ] **Choose your PR title well:** Your pull request title is what's used to create release notes, so please make it descriptive of the change itself, which may be different from the initial motivation to make the change.
+- [ ] **Update your PR description** if the specifics of the PR have changed over time.
+- [ ] **Include transcripts or screenshots** that demonstrate the changed behavior.