Tyler Nieman
11/18/2025, 4:54 PMgt mod --interactive-rebase can sometimes create a weird situation where you can no longer use gt continue and must instead use git rebase --continue ... not sure on exact repro/conditions yet, suspect it has to do with using the e (edit) action in the rebasePylon
11/18/2025, 4:54 PMgt feedback --with-debug-context <any message>Pylon
11/18/2025, 5:14 PMgt feedback --with-debug-context <message> to send us your CLI logs and we can refer to the team to investigate šTyler Nieman
11/18/2025, 5:15 PMTyler Nieman
11/18/2025, 5:24 PMā gt feedback --with-debug-context "did an 'edit' within the interactive rebase screen (gt mod --interactive-rebase)"
Uploading log files: [========================================] 100% | Upload complete
Feedback received loud and clear :blush:
just hit ya with this.Tyler Nieman
11/18/2025, 5:30 PMā gt mod --interactive-rebase
Stopped at 3d12344d3... my commit message
You can amend the commit now, with
git commit --amend
Once you are satisfied with your changes, run
git rebase --continue
ERROR: Command failed with error exit code 128:
git switch -q branch-name
fatal: cannot switch branch while rebasing
Consider "git rebase --quit" or "git worktree add".Tyler Nieman
11/18/2025, 5:33 PMgt "context" - eg gt ls won't work
⢠it stops upstack from automatically restacking after you finish the rebase
easily mitigated by gt rebase --upstack after the rebase finishesPylon
11/18/2025, 6:16 PMPylon
11/18/2025, 6:18 PMgt configTyler Nieman
11/18/2025, 6:19 PM+ @withgraphite/graphite-cli 1.7.8Tyler Nieman
11/19/2025, 11:25 PM