-
Notifications
You must be signed in to change notification settings - Fork 220
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
Install of v1.8.3+ breaks when git version is < 2.31.0 #876
Comments
Looks like the cause is the recent change - #873, and it looks like old git does not support Quick fix is to continue using version 1.8.2. I will try to fix this issue for old git versions, but this is probably not a quick fix. |
That would make sense. Thanks much for taking a deeper look. I'm also looking into updating the base image used in my development environment. |
I updated the title to more accurately reflect the nature of the issue. |
Until a solution is found for older Git, a sensible error message would make developer experience better, e.g. |
I just ran into this as well. Most the docker images I use are based on node 22 using git 2.30.2, but looks like the latest version is using git 2.39.5. Gotta upgrade my docker images |
🔧 Summary
Today, when installing 1.8.3 or 1.8.4 on a fresh build of a linux container (
elixir:1.14.2
in my case <- debian base), I could not boot into my environment due to the following error:This issue seems to be related.
This other issue also seems related.
After testing, I discovered this is only broken as of v1.8.3
Lefthook version
1.8.3 and 1.8.4
Steps to reproduce
Boot into any devcontainer configured to pull latest
lefthook
and try tolefthook install
Expected results
Install completes successfully.
Actual results
Error creating directory that already exists.
Possible Solution
I'll have to dig a bit deeper before I have relevant feedback, but answers may lie in this PR that closed the related first issue mentioned above.
For the time being, I'm pinning my
lefthook
usage at1.8.2
until this is resolved.Logs / Screenshots
The text was updated successfully, but these errors were encountered: