-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gitlens doesn't work over UNC #208
Comments
@jez9999 While I don't have a need for this (nor an easy way to set this up), I'd like to be able to support this (assuming it isn't a massive amount of work). Can you please provide some logs and any other information you have about where this breaks? |
@jez9999 any update on this? |
How do I get logs? |
The error I mentioned above occurs when the GitLens pane is in History View, and you click refresh. Also in Repository View when I try to expand the "2 files changed" tab I get the same error. There may be other times when it happens too. |
This should be fixed in 7.2 |
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. |
I have a project I host on a remote server and access over a UNC share. When I open its project folder in VS Code, Gitlens doesn't work. If I click refresh in the Gitlens pane, the following error comes up:
I'm guessing this is to do with UNC paths beginning with
\\
? It would be nice if Gitlens supported this.The text was updated successfully, but these errors were encountered: