Disruptive context switch to GitLens during interactive rebase via terminal

[ignat980]

Description

In v17.7.1, When doing interactive rebases via terminal, the nice editor would open, I could choose what I want, and then its fine.

But now with the new editor in v17.8.0, the terminal gets closed, it switches me to Gitlens, the UI is more confusing than before (at least the drag and drop indicators, the text is WAY to wide, among a myriad of other UX issues), and there is no setting to go back to the previous design.

I am forced to install an older extension version.

Please bring back the previous rebase editor and do not change the context I am in. At the very least add a setting to use previous design.

GitLens Version

17.8.0

VS Code Version

Version: 1.107.0 (user setup)
Commit: 618725e67565b290ba4da6fe2d29f8fa1d4e3622
Date: 2025-12-10T07:43:47.883Z
Electron: 39.2.3
ElectronBuildId: 12895514
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.19045

Git Version

git version 2.49.0.windows.1

Logs, Screenshots, Screen Captures, etc

I already re-installed v 17.7.1, but here's your screenshots from https://help.gitkraken.com/gitlens/gitlens-release-notes-current/

[clodoaldofavaro]

Same thing there, was wondering if anyone else was annoyed by this change. Anyway we can disable this?

[colbymelvin]

EDIT: I think the OP and my issue might be fixed by the imminent patch release mentioned here?

I have a related, additional issue. When context switches to GitLens during a rebase (OP), I'm getting upsold on a Pro subscription to use the Commit Graph feature.

This is super annoying and disruptive. I can't even dismiss the popup, I can only click the "Continue" button (nevermind the fact that it's black text on a black background and I can't visually read it).

I use GitLens for annotations and file history, I do not want GitLens to inject itself in my git CLI operations. Injecting your upsell in a workflow that I don't typically associate with GitLens is a bad place to do that.

[d13]

Sorry about that, please update to 17.8.1 and you should be all set

[ignat980]

@d13 thanks, but I'm gonna stay on 17.7.1 for a bit until the previous UI and terminal flow is able to be used again (the release notes comment "GitLens now handles rebases internally rather than routing through terminal" is VERY ambiguous in how typical existing terminal flows (not only rebase, but also merge, revert, and branch delete) will be handled while GitLens is installed)

[eamodio]

@ignat980 That change is just how GitLens invokes git rebase when you trigger a rebase through the UI. So instead of opening a VS Code terminal and "typing" git rebase, we just shell out directly to git rebase. If you use the terminal, nothing should change.

[eamodio]

@colbymelvin We'll have to get that theme issue fixed up -- can you tell us what theme you are using? Clicking "Continue" does dismiss that popup and let you use the Commit Graph for few days (without you needing to do anything at all -- other than click Continue)

[ignat980]

@eamodio thanks for the explanation, I still prefer the previous UI design compared to the new one for the interactive rebase

[eamodio]

@ignat980 What do you prefer about the old design vs the new? The new design is certainly more dense (thought about adding a density option), but are there other things?

[ignat980]

@eamodio the main thing is the new design showing more of the body of the commit message, where the first line was already enough. Also the screen is a lot more wider somehow, I have to move my mouse more in the new design. It's less clear that the choices are drop-down and draggable. Previous colors were more muted which I preferred. Shortcuts were more clear with the larger font and dedicated clear section, unlike now where shortcuts feel a lot more hidden. When I reinstall the new version and try the new design again I may have more comments but these were the first things that stood out to me.