Require PR bodies to use the template's exact headings - #528
Merged
Merged
Conversation
The PR description style guidance described the template loosely, and two release PRs were opened with a different, ad-hoc section structure instead of the actual headings in PULL_REQUEST_TEMPLATE.md. Makes verbatim use of the template's headings an explicit hard requirement. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
1 participant
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 kind of change does this PR introduce? (Bug fix, feature, docs update...)
Docs update (
AGENTS.md).The "PR description style" guidance describes filling out the PR template loosely, without requiring its exact headings. Two release PRs (#526, #527) were opened using a different, ad-hoc "Description / Type of change / Checklist" structure instead of the template's actual sections.
🆕 What is the new behavior (if this is a feature change)?
Adds a hard requirement: PR bodies must use
.github/PULL_REQUEST_TEMPLATE.md's exact section headings verbatim, including for small or maintainer-authored PRs such as release/version-bump PRs.💥 Does this PR introduce a breaking change?
No.
🐛 Recommendations for testing
Docs-only change; no build or test impact.
📝 Links to relevant issues/docs
N/A
🤔 Checklist before submitting
🤖 Generated with Claude Code