Skip to content

GitLens does not handle Windows junctions #1328

@sweiss3

Description

@sweiss3

Hi,
My setup contains a repo with multiple submodules, with junctions made from submodule A to submodule B.

GitLens is unable to show history of the file when it is accessed through the junction.

Sample directory structure:

Repo1
|- R2 (submodule)
   |- test2.txt
|- SomeFolder
   |- LinkToRepo2 (junction to R2)
       |- test2.txt (from R2)

Navigating to SomeFolder/LinkToRepo2/test2.txt in VSCode results in the following error in GitLens deubg window:

Git Command failed: C:\Program Files\Git\cmd\git.exe -c core.longpaths=true -c core.quotepath=false -c color.ui=false blame --root --incremental -- SomeFolder/LinkToRepo2/test2.txt • no such path 'SomeFolder/LinkToRepo2/test2.txt' in HEAD • 35 ms

I know this is quite a unique case - maybe there's a way I could intercept the command to resolve the correct file and repo on my own?

Metadata

Metadata

Assignees

Labels

help wantedWant community input and/or pull request

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions