-
Notifications
You must be signed in to change notification settings - Fork 30.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Git: Open changes" action and button gone missing :( #131739
Comments
Installed 1.60.0 and still no way to Open Changes on the current file 😫 |
I met the same problem, could anyone help? |
/gifPlease I can't reproduce this -- can you reproduce with 1.61 (insiders)? If so, can you attach a gif please? |
Here is a screencast showing my installed extensions and the issue itself. OpenChangesActionIsGone.mp4 |
This had always been working perfectly until ~2 month ago.
Unfortunately it shows a diff with different left/right references than what "Open changes" does, which doesn't allow to stage/unstage changes. Again, the situation is: |
I am observing the same behaviour on two Windows devices running VSCode 1.60.2. For me however, the button doesn't show up in any scenario; not when running with a WSL remote, not when using remote-containers, and not with no remotes either. System information: VS Code version: Code 1.60.2 (7f6ab54, 2021-09-22T12:00:31.514Z) System Info
Fetching remote diagnostics for 'Dev Container: C++' failed: Canceled
Extensions (16)
A/B Experiments
|
Issue is still present after yesterday's version update
|
I'm surprised there are so few vscode/WSL users that the incidence is not higher. |
Just upgraded to 1.61.2 and issue is still present. System information:
Extensions (27)
A/B Experiments
|
@CComparon, sorry about that. I have tracked this regression down to the fix for #26425. For the time being, I have reverted that fix (4297ff8) until I refactor it to avoid such a regression. The fix will be released in Insiders next week, and in Stable next month. |
@lszomoru Thanks a ton! |
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
I remember seeing an issue mentioning that regression a month or two ago, it got fixed, but somehow didn't make its way into the 1.59.1 release.
Thanks,
Cyril
The text was updated successfully, but these errors were encountered: