Repository navigation
Add submit --down to submit only up to a branch - #39
Merged
Merged
Conversation
Push force pushes a set of branches in one atomic git push, each with --force-with-lease against the remote tip the caller expects, so a remote that moved since the last fetch refuses the whole push.
DomBlack
reviewed
Oct 15, 2026
| {"ab", "stack absorb"}, | ||
| {"rs", "stack restack"}, | ||
| {"ss", "stack submit"}, | ||
| {"ss", "stack ss"}, |
Owner
There was a problem hiding this comment.
could this alias not just be stack submit --stack ?
StillAyo
force-pushed
the
submit-up-to-branch
branch
from
October 15, 2026 13:14
2146636 to
0c7b535
Compare
StillAyo
changed the title
git stack submit --down pushes the current branch and every branch below it, and leaves the ones above alone, so the bottom of a stack can go for review while the top is still moving. Naming a branch does the same up to that branch. A plain submit still pushes the whole stack. gh stack submit always pushes every branch, so the whole stack still goes through it. With --down and branches above, submit pushes those branches itself in one atomic, leased git push, creates their missing PRs through the forge, and runs gh stack link with the PR numbers so they join the stack on GitHub without pushing anything else. gh stack's editor only exists inside its submit, so new PRs there take their titles from their commits unless --ai or supplied texts say otherwise. stack_submit gets matching down and branch inputs.
StillAyo
force-pushed
the
submit-up-to-branch
branch
from
October 15, 2026 13:19
0c7b535 to
e1a71bb
Compare
StillAyo
changed the title
DomBlack
approved these changes
Oct 15, 2026
DomBlack
enabled auto-merge (rebase)
October 15, 2026 13:27
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.
Add
--downtogit stack submitto push part of a stack, i.e. the current branch and everything below it. This leaves the above branches alone, the waygt submitdoes.This allows for the bottom of a stack to be sent for review while the top is still being worked on.
Existing state
submitalways submitted the whole stack, becausegh stack submithas no way to scope it and always pushes every branch.Change
git stack submit --downsubmits the current branch and every branch below it.git stack submit <branch>does the same up to the named branch.submit/git ss: unchanged, throughgh stack submit. So is--downfrom the top of the stack.submitdoes the work itself:git push, each with--force-with-leaseagainst its remote tracking tip (newgit.Client.Push);--aitext, otherwise a single commit's subject and body, the same way gh stack fills them in;gh stack linkwith the PR numbers so they join the stack on GitHub (newSubmitter.Link).stack_submitgetsdownandbranchinputs.docs/architecture.mdanddocs/mcp.mdare updated.