We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Running lefthook install in a repository that is a linked worktree (not the main worktree) causes an error like:
lefthook install
$ lefthook install Error: mkdir /home/markrian/my-linked-repo/home/markrian/my-main-repo/.git/info: no such file or directory
1.2.7 c88a009
git worktree add ~/path/to/new/repo
~/path/to/new/repo
$ lefthook install Error: mkdir /home/markrian/path/to/new/repo/home/markrian/my-main-repo/.git/info: no such file or directory
If you try the same with lefthook 1.2.6, it succeeds without error.
If you run lefthook install from the main worktree, it also succeeds without error.
lefthook install should work without error.
There's an error.
I suspect #414 is the source of this breakage, since it adds a mkdir call.
mkdir
n/a
The text was updated successfully, but these errors were encountered:
Hey! Thank you for the issue. I will take a look and try to fix it today-tomorrow.
Sorry, something went wrong.
Than you a lot for a clean bug description! I will release the fix with version 1.2.8 soon
fix: Don't join info path with root (#418)
d7b107c
Closes #417
Successfully merging a pull request may close this issue.
🔧 Summary
Running
lefthook install
in a repository that is a linked worktree (not the main worktree) causes an error like:Lefthook version
1.2.7 c88a009
Steps to reproduce
git worktree add ~/path/to/new/repo
~/path/to/new/repo
)lefthook install
If you try the same with lefthook 1.2.6, it succeeds without error.
If you run
lefthook install
from the main worktree, it also succeeds without error.Expected results
lefthook install
should work without error.Actual results
There's an error.
Possible Solution
I suspect #414 is the source of this breakage, since it adds a
mkdir
call.Screenshots (if appropriate)
n/a
The text was updated successfully, but these errors were encountered: