Describe the bug
When getting the .git/config, it assumes that it's in the work directory:
| constgitConfig=Uri.file(`${pathToWorkspace}/.git/config`); |
If somebody like me is a fan of worktrees, they won't have a .git folder in their workspace. Instead, .git will be a text file containing something like this:
gitdir: /home/rasmus/Projects/repo/main/.git/worktrees/branch
When running the codecov extension in a linked worktree, that has such a .git file in lieu of a directory, that will result in the following error:
Error: ENOTDIR: not a directory, open '/home/rasmus/Projects/repo/branch/.git/config'
To Reproduce
Steps to reproduce the behavior:
- Clone a repository
- Run
git worktree add -B branch ../branch - Open
../branch in vscode with the codecov extension enabled
Expected behavior
The codecov extension should correctly resolve the git repository, and work as well in linked worktrees as in main worktrees.
Describe the bug
When getting the
.git/config, it assumes that it's in the work directory:vscode/src/coverage/coverage.ts
Line 140 in f708fe8
If somebody like me is a fan of worktrees, they won't have a
.gitfolder in their workspace. Instead,.gitwill be a text file containing something like this:When running the codecov extension in a linked worktree, that has such a
.gitfile in lieu of a directory, that will result in the following error:To Reproduce
Steps to reproduce the behavior:
git worktree add -B branch ../branch../branchin vscode with the codecov extension enabledExpected behavior
The codecov extension should correctly resolve the git repository, and work as well in linked worktrees as in main worktrees.