Repository navigation
chore: use the org PR template - #60
Merged
Merged
Conversation
Delete this repo's own PR template, so new PRs start from the org default merge brief in ST0x-Technology/.github. Co-Authored-By: Claude Opus 5.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.
Deletes this repo's own PR template, so new PRs start from the org merge brief in ST0x-Technology/.github#12.
Live effect: new PRs opened on GitHub start from the org template · Risk: low (no money path, no keys or IAM, docs only, easy to undo) · Ships: on merge
Risks
gt submitonly reads templates inside the repo, so PRs opened from the Graphite CLI will start with an empty body here.Rollout
🤖 Generated with Claude Code