CODEWITHSUNDEEP
visual-studio-codegitlens
vjalle
vjalle

Reputation: 983

GitLens in VS Code: no inline blame info anymore

After several updates, and installing other extensions like Error Lens, I noticed that GitLens stopped working. There is no blame information displayed at the line ends anymore. Error Lens continues working. I'm not using the plus features and are not logged in to a GitLens+ account. According to its documentation, the inline blame is not a plus feature and should work without subscription. When installing Code on another computer and synchronizing the settings, GitLens worked for a short while and then the inline blame messages disappeared.

Is this a known issue? What can be the reason?

Edit: GitLens inline blame works in the diff editor, opened from the source control view. The blame is also displayed in the status bar, and "Toggle Line Blame" also works as expected.However, neither of them works when opening a file normally. No status bar message, no inline blame, toggle line blame has no effect. It's enabled in the configuration. Disabling all other extensions and leaving only GitLens enabled has no effect, either.

Upvotes: 24

Views: 21621

Answers (6)

Bruno P
Bruno P

Reputation: 1

I was able to solve my problem by left-clicking on the GitLens extension and selecting "Switch to Release Version."

Upvotes: 0

Elizandro - SparcBR
Elizandro - SparcBR

Reputation: 358

Git blame was not showing on status bar for me when I used my smaller monitor. In the big monitor it would show. So I disabled some extensions that was taking up space in the status bar and it worked.

Upvotes: 1

bstrihova
bstrihova

Reputation: 131

If inline blame of GitLens doesn't show anymore, I found it gets fixed if you create an empty file in the root of your repo called .git-blame-ignore-revs. This works for me on a MacBook.

I found the solution here: https://github.com/gitkraken/vscode-gitlens/issues/1143#issuecomment-758947995

Upvotes: 11

cruni505
cruni505

Reputation: 41

I was facing the same issue, the workorund was moving all my projects to C drive, I hope this pelps someone else.

Upvotes: 4

Jonathan Sanchez
Jonathan Sanchez

Reputation: 9474

I've been struggling with the same issue, for some time, but finally found my solution.

Hope this helps.

you have to exit ZEN mode

Like this, find zen at the bottom of the vscode status bar

enter image description here

then Change to Review Mode

enter image description here

Upvotes: 29

vjalle
vjalle

Reputation: 983

Okay figured the root cause. It's connected to virtual drives assigned to folders with the subst command.

  • Open the workspace through the virtual drive and then open a file for editing from Explorer or ctrl-p: no blame info.
  • Open the workspace through the virtual drive, and then open a file from the Source Control view by right-click / Open File: inline blame works
  • Open the workspace through the original long path (no virtual drive) and then open files in any way: inline blame works

It seems to be an issue in the recent versions of the extensions. I'm going to create a ticket for it.

Upvotes: 14

Related Questions