'Visual Studio Code source control not showing changes

Visual Studio Code source control panel is empty when I click on it. Nothing to expand and nothing to click on.

Things I've tried:

Uninstalled/Reinstalled Git
Uninstall/Reinstalled VS Code
Removed extensions folder

Solution 1:^[1]

I fixed it by doing the following:

go to file -> preferences -> settings
Expand features
Click SCM
Click Always Show Providers
I then messed around with left panel (can't remember what I did) but I noticed my changes now show
I unchecked the setting I checked earlier and all is well now even after restarting VS Code

Solution 2:^[2]

I had this problem 2-3 times for the last 2 years (OS -> Linux Mint). The changes on any file didn't appear to the source control nor have they been marked on the line I've edited. When manually go to "Source control" and click on the refresh button they appear but the lines that I had change didn't light up (there were no visual marking on the files after editing them). This happened when I switched to a different branch while the workspace was open to the 2 monitors at the same time. Or when working on several projects (opened 2-3 or more VS Code instances). The scariest thing was that it didn't work not only for one repository(project) but for all of them. I've read alot on the subject and tried everything that I found and think of. There is some issue with git path mapping or something.

The thing that I tried:

reload VS Code
restarting VS Code
disable all extensions
enable/disable all git related options in (file -> preferences -> settings)
deleting (folders and files) and cloning the repository
updating git
removing and installing git
restarting PC (don't judge me I was desperate)

But the only solution that worked for me was:

open VS Code (if open, don't close it)
go to the directory where you keep your repositories (not from VS Code but from you file explorer).
go one folder above it (if you are in .../{{some folder}}/{{you repos}}, go to ../{{some folder}})
then open you repositories containing folder (/{{you repos}}) by right click -> open with VS Code
wait until everything loads. The Source Control will mark alot of changes, don't worry about it.
then close VS Code (all windows (instances), because it will open a new instance)
after that go to the directory where you keep your repositories again and right click and open with VS code the repository of you choice. Now at this point the Source control will start working properly.

Solution 3:^[3]

I had a similar issue. It seems vs code has two source control extensions. When I clicked View -> SCM it opened an extension with changes displaying.

source control extension 1

source control extension 2

Solution 4:^[4]

Dude, just lost an hour because my SCM in VSCode randomly stopped showing anything today. I restarted everything, tried git init, everything on the forums. Made sure Git built in extension is enabled, mine was already enabled so I was totally lost.

All I had to do was disable and then reenable the built in Git extension. and it fixed it.

Go to Extensions.

Filter by "built in".

Click the gear icon by Git, and click disable.

Then click it again, and click enable.

Here is a screenshot reference

Solution 5:^[5]

What worked for me was going to my "code" folder where I keep all my repos, right-clicking on the folder containing the repo I want and opening that folder with VS Code.

The VS Code window for this specific repo was closed. I did have another window for a different repo open. As soon as the window opened, the changes showed up in source control and I was able to commit, push and everything else like normal.

Solution 6:^[6]

I had this problem in a repository not as a problem from config but because I had a coverage folder with thousands of files not tracked and it seemed to slow the process of checking that out too much.

So I added that folder to .gitignore and it started working again.

Solution 7:^[7]

I faced this problem when I opened a repo in a directory inside symlink.

My solution: just open this directory in original destination without any symlinks

Solution 8:^[8]

Restating my Vscode And Giving time to load properly Solved my Problem

Solution 9:^[9]

I had the same problem. What I did was:

Open another folder with File -> Open Folder...
Close the VSC
Open VSC
Open the original folder with File -> Open Folder...

After this I saw that the source control started loading and my changes came back.

Hope this works for you.

Solution 10:^[10]

I couldn't see any changes in while trying git status. I opened changed files in text editor and they were not changed either. That lead me to conclusion that changes can't be seen by the system (and therefore by git).

The Autosave option was disabled, simply saving the changes helped.

That was my beginning with VSC, in Pycharm never had such problem.

Solution 11:^[11]

I had this problem, because I was changing files one folder down from where I opened Visual Studio Code.

Solution- open Visual Studio Code without a location, File/Open Folder - open the folder I am directly working out of.

Unstaged changes now show in the direct folder I'm working in. Unstage changes previously auto-staged by Visual Studio Code when working on a nested project directory to see them (open a Terminal and run git reset).

Solution 12:^[12]

I encountered the same issue, and I fixed that by removing the files.watcherExclude property in settings.json file. Because the value of files.watcherExclude became { "**/**/*": true } somehow.

// settings.json
 
// remove or comment next line
// files.watcherExclude: { "**/**/*": true }

Solution 13:^[13]

For me, the files were in WSL (Windows subsystem for linux) but I was not opening the folder as such.

in the bottom left, click the green >< symbol, then click "reopen folder in WSL"

VSC remote mode image

presto.

Solution 14:^[14]

Go to View -> Terminal
cd to root folder, and run git status and see if you have any errors

I had a unsafe repository fatat error, as my repo was on a network drive. Did as suggested by git to add an exception and it fixed the issue.

Solution 15:^[15]

In my case, somehow, the Source Control Repositories option, available under the 3 dots ... on the SOURCE CONTROL tab, was no longer selected.

All I had to do was press the ... and select Source Control Repositories, then select the correct repo, and all the changes were again listed.

Solution 16:^[16]

Try opening project or folder which contains git files. Later try opening your wanted folder. This sorted the issue for me.

Solution 17:^[17]

Double-check git is actually installed on your system. I just did a fresh install of Windows 11 the other day, and although one of the development tools I installed thereafter downloaded and supposedly installed git in Windows, actually, it never installed it. Fail!

Solution 18:^[18]

I fixed this issue by toggled-on the AutoSave feature in VSCode via File > AutoSave. I noticed that the badge on the github does not show up until the file is actually saved first.

Solution 19:^[19]

The actual running node location can be found with this command

node -e "console.log(process.execPath)"

this will output the executed bin compiled nodejs path. which will not really much help you.

what will help you is knowing the node version you are running and check the source code of the module you want. http.js .

or debug nodejs in real time. break point on the http module and then get into the module itself with the help of the debugger. check out this guide

Solution 20:^[20]

Well this depends on which operating system you are using:

If you are on windows it's in C:\Program Files\nodejs\node_modules\npm\node_modules or at least I think...

If you want to know on linux check out this question on the askubuntu.com website. In this question, someone answered that it was in

/usr/local/lib/node or /usr/local/lib/node_modules

Tejas Lotlikar

There is a high chance that on mac, the location is the same as linux because macOS is based upon some "ancient" linux dist.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution	Source
Solution 1	Post Impatica
Solution 2	Mkey5
Solution 3
Solution 4	Dharman
Solution 5	Jeffrey Saari
Solution 6	nck
Solution 7	Nick Lefterov
Solution 8	Raaj_BN
Solution 9	Johols
Solution 10	Daniel R
Solution 11	coder9833idls
Solution 12
Solution 13	Leigh Boyd
Solution 14	Manpreet
Solution 15	Telmo Dias
Solution 16	Chandrahasa Reddy
Solution 17	John Rix
Solution 18	Robie
Solution 19
Solution 20	Luke Beveridge

'Visual Studio Code source control not showing changes

Solution 1:[1]

Solution 2:[2]

Solution 3:[3]

Solution 4:[4]

Solution 5:[5]

Solution 6:[6]

Solution 7:[7]

Solution 8:[8]

Solution 9:[9]

Solution 10:[10]

Solution 11:[11]

Solution 12:[12]

Solution 13:[13]

Solution 14:[14]

Solution 15:[15]

Solution 16:[16]

Solution 17:[17]

Solution 18:[18]

Solution 19:[19]

Solution 20:[20]