Repository navigation
Fix formatting in PR template checklist - #5024
Merged
copybara-service[bot] merged 1 commit intoOct 15, 2025
Merged
Conversation
Contributor
Author
|
Was it meant to improve readability? |
Collaborator
|
It was created 3 years ago. We can make each line as a single line. I have no strong opinion. |
vfdev-5
approved these changes
Oct 13, 2025
cgarciae
approved these changes
Oct 14, 2025
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.
What does this PR do?
Follow-up of ab90975.
This pull request makes a small change to the
.github/pull_request_template.mdfile, improving the formatting of the checklist section by consolidating multiline checklist items into single lines for better readability.I found the checklist in current PR template is somewhat broken as below:
Checklist
checks if that's the case).
discussion (please add a
link).
documentation guidelines.
(No quality testing = no merge!)