docs(agent): stack checkout no longer takes --author or --branch-prefix - #12633
Merged
mergify[bot] merged 1 commit intoSep 1, 2026
Merged
Conversation
Contributor
Merge Protections🟢 All 6 merge protections satisfied — ready to merge. Show 6 satisfied protections🟢 🤖 Continuous Integration
🟢 👀 Review Requirements
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
jd
approved these changes
Sep 1, 2026
remyduthu
approved these changes
Sep 1, 2026
Contributor
Merge Queue Status
This pull request spent 5 minutes 58 seconds in the queue, including 4 minutes 47 seconds running CI. Required conditions to merge
|
63 tasks
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.
mergify stack checkoutwas reworked in the 2026.8.28 CLI:--authorand--branch-prefixare gone, the positional argument now takes either a stack'sremote branch name or the URL of any pull request in the stack, and
--branchderives its default from the stack branch rather than from the stack name. The
Team Adoption page still told a teammate to run
mergify stack checkout feat/their-feature --author their-login, which the CLInow rejects, and two pages listed
checkoutamong the commands that accept--branch-prefix. It is the one stack command that no longer does.Separately, both the Concepts page and the merge queue's Stacked Pull Requests
page presented the
Depends-On:marker as something every pushed stackcarries, and as what makes the queue treat the chain as a unit. A stack pushed
with
--github-nativecarries no such marker, because GitHub's stacking APIholds the ordering instead, and the queue then handles it as a GitHub-native
stack: queued per member, landing bottom up. Both pages now say so and point at
the section that already documents that path.
Evidence:
public/cli-schema.jsonfor the flag and argument changes, and itsown
--github-nativehelp text for the missing header.Open question: whether the branch-name form of the target deserves an example.
The schema says
checkoutaccepts "its remote branch name", but a stack has oneremote branch per commit under a
{prefix}/{name}/path, so which string thatmeans is not obvious. I documented the pull request URL form, which the schema
states unambiguously, and mentioned the branch form without an example rather
than guess at one.