Use correct checklist syntax in PR template#296
Merged
seddonym merged 1 commit intopython-grimp:mainfrom Jan 19, 2026
Merged
Conversation
Use correct checklist syntax
CodSpeed Performance ReportMerging this PR will not alter performanceComparing Summary
Footnotes
|
There was a problem hiding this comment.
Pull request overview
This PR fixes the checklist syntax in the GitHub pull request template to render properly as interactive checkboxes. The change adds the required dash prefix (-) to each checklist item, converting from the incorrect [ ] format to the correct GitHub markdown syntax - [ ].
Changes:
- Updated all 5 checklist items in the PR template to use proper GitHub markdown checklist syntax
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Collaborator
|
Nice, thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Instead of current renderning like this ⬇️
[ ] Add tests for the change. In general, aim for full test coverage at the Python level. Rust tests are optional.
[ ] Add any appropriate documentation.
[ ] Add a summary of changes to the
latestsection at the top ofCHANGELOG.rst. (If it's not there, add it.)[ ] Add your name to
AUTHORS.rst.[ ] Run
just full-check.You'll get a nice checklist like this ⬇️
latestsection at the top ofCHANGELOG.rst. (If it's not there, add it.)AUTHORS.rst.just full-check.Please merge it after #295