vscode: Changed files don't appear under Source Control > Changes
Does this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.85
- OS Version: MacOS 14.1.1
Steps to Reproduce:
- Open a large project with a lot of files.
- Edit and save a file.
- Go to Source Control, and the file doesn’t appear under Changes.
- However, the number bubble DOES appear on the Source Control icon, with a “1 Pending Changes” tooltip. And the context menu items on the Changes header work, like “Open Changed Files”.
This seems to only happen on large projects.
Started in 1.85.0. Happens with extensions disabled. Doesn’t happen in 1.84.2.
I tried to use “Report an Issue” for this, but nothing happened when I clicked the submit button.
About this issue
- Original URL
- State: closed
- Created 7 months ago
- Reactions: 12
- Comments: 28 (9 by maintainers)
The fix for this issue will be included in VS Code 1.86.
Same for me after latest update. It seems like the source control view is loaded exactly once and then not updated again. Any operation done in the source control view (staging, commiting, etc) is not reflected at all even though the git operation is actually performed behind the scenes.
I confirm and would like to add that, generally, the view of changes and staged changes does not refresh.
It still persists in 1.86.2
Hello! The problem still persists and occurs every time I try to push my changes to the repository. Please consider making fixing it a higher priority.
Does the issue get resolved if you set
scm.showIncomingChangesandscm.showOutgoingChangestofalse? The error above seems to indicate that we cannot locate a branch. Could you share more details on the branch? Do all of you see that error in the developer console?I have experienced having this issues whenever my VS Code updates.
Reinstalling fixes it.~edit: reinstalling only fixes it when going back to an older version. I am experiencing issues when on 1.85.2 Installing 1.84.2 seems to fix it. Make sure to set update: mode to manual or it will automatically update to the latest.
I’ve been working on Code Insiders since the last message. So far, I haven’t noticed the issues.
@lszomoru Seems to be working so far