vscode: Stage Selected Ranges broken again?

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.66.2
OS Version: 11.6 (Big Sur)

Steps to Reproduce:

Make some changes in a file at two different places (“1st changes” and “2nd changes”)
Open Source Control Sidebar and select file you just changed to see the diffs for 1st & 2nd changes in the editor.
Select the red and green diff of 1st changes, right click the selection, and choose “Stage selected ranges”. RESULT: As expected, the diff of 1st changes will disappear from the editor, the current file will appear under Staged Changes in the sidebar, and the diff of 1st changes will be visible in “Staged Changes” editor.
Go back to the “Changes” editor and repeat step 3 for 2nd changes. EXPECTED RESULT: The same thing should happen for 2nd changes. ACTUAL RESULT: The same thing does happen for 2nd changes, but 1st changes are reverted and move from Stage Changes to Changes (i.e., 2nd changes are staged, 1st changes are unstaged.).

About this issue

Original URL
State: open
Created 2 years ago
Reactions: 18
Comments: 16

Most upvoted comments

I commented in 2022 and I’m back now in 2024 to say I’m still regularly experiencing troubles staging additional lines after staging some. Sometimes it forgets what I staged and instead of staging additional lines on top of what was previously staged, the selective staging overrides the currently staged contents for that file entirely, making it kinda pointless for complicated staging operations.

I’ve also noticed it gets confused by multiple cursors if you try to stage lines from many places/selections/cursors and only stages the first selection properly, if at all.

I’m so annoyed at this point if I have anything complicated to stage I just open the Terminal and run gitui instead. 😕

Version: 1.85.1 (user setup)
Commit: 0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2
Date: 2023-12-13T09:49:37.021Z
Electron: 25.9.7
ElectronBuildId: 25551756
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.22621

darkvertex on Jan 11, 2024

I am experiencing the same issue, although I usually use the green (addition) and blue (change) colored ribbon-thingies (and red triangles for deletion) that appear on the left side of the code after changes. Clicking on them lets me interactively stage a single change from a file, but sometimes trying to stage more than one change, causes the previously staged changes to unstage. It’s really annoying. I thought it could be a GitLens issue (since I also use it as well), but I’ve been told this feature comes from VSCode itself.

DevilXD on Sep 6, 2022

This is also happening to me in version 1.77.3, Linux x64. I’m not attempting to stage changes on the left pane – only on the right pane. It was such a nice feature in the previous version I was using, where I never had any issues with the feature. Some notes about it:

To get VS Code to “accept” the staging (react at all and no longer show the change), you have to switch to another tab and back. I like to switch to the Staged Changes version of the file and then back to the Changes version, in the Source Control file selector. Doing that gets it to behave similar to the way it did when there wasn’t a problem. EDIT: I found that just alt-tabbing to any other window and back to VS Code makes the Working Tree tab update to show the staged change properly, the way it used to work, without having to alt-tab or anything else.
However, if you stage multiple selections, only the last one staged actually gets staged. So, you have to get it to update after every staging, in order to get it to accept every staging.
Another alternative is to use the line staging functionality in the “main” file tab, available in the file Explorer. Click the colored lines that show up to the left of the changed lines and to the right of the line numbers (if those are turned on). Use the plus sign button to stage the change in the line. That functionality still works. (But I prefer the side-by-side diff view. I hate that it’s not working).

Pulseczar1 on May 23, 2023

If you navigate away from the file after staging a selected range, it works. The issue needs to be fixed, but this crappy workaround helps in the interim.

bandtank on Mar 4, 2023

I’m seeing this issue in WSL mode.

guanzo on Sep 27, 2022