-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Closed
Description
Description
In our environment, we have Git repositories checked out inside a top-level repository (but not defined as sub-modules).
Gitlens used to work well with them until a couple of days ago.
This is the error I'm seeing now:
[2023-11-21 09:04:52.304] [<path>/top_repos/sub_repos] Git Command failed: /bin/git -c core.quotepath=false -c color.ui=false blame --root --incremental -w -- <path>/top_repos/sub_repos/file.txt • no such path '<path>/top_repos/subrepos/file.txt' in HEAD [83ms]
I've tested on the pre-release as well, and it still fails.
Thanks,
Sébastien.
GitLens Version
v14.5.0
VS Code Version
1.83.0
Git Version
2.33.0
Logs, Screenshots, Screen Captures, etc
In the log, it looks like Gitlens is looking for the file in the top repository instead of going into the sub repositories like it used to:
[2023-11-21 09:13:33.886] [ 547] GitLineTracker.updateState(e=60, t=file:///<path>/top_repos/sub_repos/file.txt)
[2023-11-21 09:13:33.886] [ 548] GitProviderService.getBlameForLine(e=GitUri(file:///<path>/top_repos/sub_repos/file.txt repoPath=<path>/top_repos), t=60, i=false)
gadzhov
Metadata
Metadata
Assignees
Labels
verified ✔VerifiedVerified