Standardize pull request guidance - #47
Merged
Merged
Conversation
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.
Background
Recent Stack pull requests consistently explain their context, implementation, validation, and review concerns, but each author currently has to recreate that structure manually. Repository-local guidance should make the expected format available to every contributor and coding agent.
Implementation Approach
.github/pull_request_template.mdwith the established four-section structure.AGENTS.mdto require English pull request titles and bodies.Testing Approach
git diff --checkAGENTS.mdreferences the repository-local template and explicitly requires English pull request titles and bodies.Review Perspectives / Points of Concern