Add agent instruction: do not create stacked pull requests#107778
Open
alexey-milovidov wants to merge 1 commit into
Open
Add agent instruction: do not create stacked pull requests#107778alexey-milovidov wants to merge 1 commit into
alexey-milovidov wants to merge 1 commit into
Conversation
Pull requests must target `master` directly (or, in rare cases, a release branch), never another feature branch. CI only runs for pull requests whose base is `master` or a release branch, so a pull request stacked on another feature branch gets no checks. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
|
Workflow [PR], commit [4d4cbcf] Summary: ✅ AI ReviewSummaryThis PR adds an agent instruction to Final VerdictStatus: ✅ Approve |
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.
Adds a rule to
.claude/CLAUDE.mdinstructing the agent not to create stacked pull requests. Every pull request must targetmasterdirectly (or, in rare cases, a release branch), never another feature branch.Motivation: the PR CI workflow (
.github/workflows/pull_request.yml) only triggers for pull requests whose base ismaster, and release branches are covered by their own workflows. A pull request stacked on top of another feature branch therefore receives no checks at all, which is easy to do by accident and confusing to diagnose.Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):
...