René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`gh stack rebase -i` - allow interactive rebasing","articleBody":"Support `-i` for rebasing stacks. \n\nI ❤️ rebasing, and doing no-edit amends. When I do that in a branch low in the stack, the higher layers end up with \"duplicate-ish\" commits that conflict. The solution during a normal rebase is to drop that new duplicate. Here's an example\n\n### Initial State\n\nbranch-a\n`main -\u003e commitA (111aaa)`\n\nbranch-b\n`main -\u003e commitA (111aaa) -\u003e commitB (222bbb)`\n\n### Change in `branch-a` and `git commit --amend`'d\n\nif I go to `branch-a` and make a change using `git commit --amend` I'll end up with this:\n\nbranch-a\n`main -\u003e commitA (112aaa)`\n\nbranch-b\n`main -\u003e commitA (111aaa) -\u003e commitB (222bbb)`\n\n### Finally, rebasing `branch-b`\n\nThen when `branch-b` gets rebased, it looks like this:\n\n`main -\u003e commitA (112aaa) -\u003e commitA (111aaa) -\u003e commitB (222bbb)`\n\nAgain, the solution is simply to `drop` `commitA (111aaa)`, as that's the old one. \n\nBut I can't do that with `gh stack rebase`. ","author":{"url":"https://github.com/wmcnamee-coreweave","@type":"Person","name":"wmcnamee-coreweave"},"datePublished":"2026-06-28T05:00:37.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/151/gh-stack/issues/151"}