Suppress message "GitLens was unable to find Git"

[thernstig]

I run VS Code in Windows but develop exclusively with the remote extensions (WSL, ssh, containers). This means I never install git in Windows. Yet, I always get this error when launching VS Code

GitLens was unable to find Git. Please make sure Git is installed. Also ensure that Git is either in the PATH, or that 'git.path' is pointed to its installed location.

It would be nice if this could be added as a config:

  "gitlens.advanced.messages": {
    "suppressGitNotInstalled": true
  },

That way I can suppress that message from showing up at every start.

[eamodio]

GitLens can't work without Git installed. So for your scenario, I would recommend disabling GitLens locally, an only leave it on in the remote.

[thernstig]

Afaik that is not possible. I just tested it .

Note that I open VS Code in Windows (without being connected to a remote). The only option I then have is to disable globally. This is then synced to all my machines, meaning Gitlens is even disabled locally/remotely for all my machines.

[eamodio]

@sandy081 is that expected? I wouldn't have expected the local enabled state to be synchronized to a remote.

[thernstig]

By the way, I have a about 20 extensions and many of them require something else to be installed to function. E.g. the docker extension requires docker, but it still does not give me an error when I launch VS Code. Every other extension handles this gracefully only giving me warning/errors/notifications or uses GUI in ways to inform me that it does not work, when actually invoking it.

[eamodio]

Can you please verify this fix in tomorrow's insiders edition?

You can install the insiders edition from here. Be sure to disable/uninstall the stable version of GitLens first.

[sandy081]

We do not sync local to remote.

This is then synced to all my machines, meaning Gitlens is even disabled locally/remotely for all my machines.

I think user is mentioning about other machines when said remote

[thernstig]

@sandy081 correct, I meant to other machines (i.e. other laptops I have). But on those other laptops, it then also disables it both locally and on ssh remotes after the sync.

But it's moot now as it seems @eamodio has fixed it :)

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.