-
Notifications
You must be signed in to change notification settings - Fork 37.2k
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buginsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsidersscmGeneral SCM compound issuesGeneral SCM compound issuesverifiedVerification succeededVerification succeeded
Milestone
Description
Does this issue occur when all extensions are disabled?: Yes (but with WSL to open a repo in WSL)
- VS Code Version: Version: 1.90.0-insider (user setup)
Commit: 5e68ffd
Date: 2024-05-15T08:29:12.858Z
Electron: 29.3.1
ElectronBuildId: 9464424
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.22621 - OS Version: Windows 11 Enterprise
Version 22H2
OS Build 22621.3447
Windows Feature Experience Pack 1000.22688.1000.0
Steps to Reproduce:
- Create a git repo with
git init - Open the repo, add and modify files.
- Open modified file in VSCode
I also tested with newly installed VSCode and it worked fine.
What I got
1.90.0-insider
1.89.1 (user setup)
Commit: dc96b83
Date: 2024-05-07T05:13:33.891Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10.0.22621

NicosGollan-cnic, bmasias1, joynal-miah, werlang, gg-sr and 10 more
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buginsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsidersscmGeneral SCM compound issuesGeneral SCM compound issuesverifiedVerification succeededVerification succeeded
