Reputation: 1275
I'm work on Linux Mint:
Screenshot of mint version
I have latest version of Visual Studio code:
Screenshot of vs code version
After new reload of OS extension GitLens disappeared: Screenshot of problem
I can't see any information in my source code, that provide this extension. Reinstallation this extension or vs code didn't apply any effect. How can i fix it?
Upvotes: 79
Views: 40944
Reputation: 21
I just selected source control on vscode's sidebar and then clicked on "start repository". This worked for me on windows.
Upvotes: 0
Reputation: 1275
This problem was related to python virtual enviroment: extension stoped indexing a lot of files of virtual enviroment. Solvation was easy: exclude virtual enviroment from project folder through moving it outside or exclude through settings
Upvotes: 1
Reputation: 6973
I had a problem with this but found a solution. Just right-click on your visual studio's sidebar and click source control to check it.
Upvotes: 0
Reputation: 4402
For me the problem was for VS Code 1.51.1 and GitLens 11 they have made the Source Control Layout as default and requires the selection of view in order to make it work as before i.e., in the VS Code sidebar (using Mac OS Catalina 10.15.2).
After update:
And your GitLens is back!
Upvotes: 227
Reputation: 1324268
Update from eamodio/vscode-gitlens issue 516:
Antivirus deleted one of the extension's files. To fix issue on Windows:
- Remove GitLens extension from VSCode
- Reload VSCode
- Close all instances of VSCode
- Delete
%userprofile%\.vscode\extensions\eamodio.gitlens-8.5.6
- Open VSCode
- Reinstall GitLens extension
For Mac users:
- remove the extension
- reload vscode
- go to
setting.json
by pressing cmd+shift+p > open user settings- delete all entries regarding the extension
- close vs code
- open vscode
- install the extension
Original answer:
Do a right click in the plugin icons column, and see if GitLens is hidden or not:
By selecting GitLens, you would find back your GitLens icon:
The OP anderson confirms in the comments
In issue 516 on Github problem was solved.
This problem was in large count of files, that GitLens extension could not read.
Exclude this path from project's directory solved my problem.
Upvotes: 9