René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Why does `gh stack rebase --upstack` include the current branch?","articleBody":"Say I have the following stack\n\n```\nmain \u003c- branch1 \u003c- branch2 \u003c- branch3\n```\n\nI'm _on_ `branch1`, and just addressed some reviewer feedback by adding a few extra commits. Now I need to do the following:\n\n- rebase `branch2` on `branch1`\n- rebase `branch3` on `branch2`\n\nI do _not_ want to rebase `branch1` on `main` right now.\n\nMy instinct is to call `gh stack rebase --upstack` while on `branch1`, where I just addressed the feedback and added commits. I was expecting that to do what I outlined above and not change `branch1` in any way.\n\nSurprisingly (to me), it did this:\n- rebase `branch1` on `main`\n- rebase `branch2` on `branch1`\n- rebase `branch3` on `branch2`\n\nCan I ask about why `--upstack` includes a rebase of the current branch on the branch under it? That actually feels a bit \"down stack\"-ish to me.\n\nIt feels like this exact workflow is going to be pretty common for me, and the current workaround is for me to `gh stack switch` up to `branch2` and _then_ run `gh rebase --upstack`, but that feels pretty unnatural to me!","author":{"url":"https://github.com/DavisVaughan","@type":"Person","name":"DavisVaughan"},"datePublished":"2026-07-02T14:17:12.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/160/gh-stack/issues/160"}