Stash Only Staged Changes Broken

[cgkp]

Description

With the last few versions of GitLens, stashing only staged changes is broken in my environment. I am doing SSH-based development on an Ubuntu system with Git version 2.25.1. My local machine from which I am connecting is running Windows 11. With GitLens through 17.1.1, I can use the Source Control UI to stage some new/modified files and then stash them. With GitLens 17.2.0 and 17.3.0 (current latest), I cannot do so, getting the incorrect message "Your Git version doesn't support stashing only staged changes. Stash all changes instead?" The bug appears to be related to this change.

Thanks for this extension!

GitLens Version

17.3.0

VS Code Version

Version: 1.102.0 (user setup)
Commit: cb0c47c0cfaad0757385834bd89d410c78a856c0
Date: 2025-07-09T22:10:34.600Z
Electron: 35.6.0
ElectronBuildId: 11847422
Chromium: 134.0.6998.205
Node.js: 22.15.1
V8: 13.4.114.21-electron.0
OS: Windows_NT x64 10.0.22631

Git Version

git version 2.25.1

Logs, Screenshots, Screen Captures, etc

No response

[eamodio]

I believe this should be fixed in tomorrow's (v2025.7.15xx) pre-release edition of GitLens, but only when stashing all changes or staged changes when there are only staged changes. If you have both staged and unstaged changes and you try to stash only staged changes, then to do that properly you need a minimum Git version of 2.35.0, otherwise all we can do is stash everything (hence the new warning).

Can you please verify this fix in tomorrow's (v2025.7.15xx) pre-release edition of GitLens? Thank you so much!

You can switch to the pre-release edition of GitLens, by clicking on the "Switch to Pre-Release version of this extension" from the Extensions view.

[cgkp]

OK, understood. I am curious as to why I am able to do partial commits using the GitLens UI up through 17.1.1 despite Git 2.25.1 being the version installed in my remote development environment.