Replies: 1 comment 2 replies
-
|
Mysteriously, GitLens has stopped complaining about the version, and now seems to work. I didn't do anything in particular, except perhaps reconnect to the remote host. Maybe that did the trick ... |
Beta Was this translation helpful? Give feedback.
-
|
mandatory step: https://stackoverflow.com/questions/55988854/alter-path-for-vs-code-remote-ssh |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! I guess when I came back to it the next day VS Code Server restarted and everything started working. Now I know what to do to force a restart :) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
GitLens works great locally on my laptop.
But I do a lot of work on a remove server (HPC), and there GitLab complains that the version of git is too old. The system-wide install of
gitis indeed fairly ancient (1.8.3.1) but I have defaultcondaenvironment that is activated by.bashrc, and that containsgitversion 2.38.1.However, GitLens doesn't appear to "see" the
gitin the activecondaenvironment -- it still complains that the version is too old. Browsing the issues I found mention of a setting that points to thegitexecutable, and discussion #1500 from May 2021 talks about agit.pathsetting but I can't find anything like that in the settings.Suggestions?
Beta Was this translation helpful? Give feedback.
All reactions