Stuck at "Locking pre-commit directory" after add a new hooks
See original GitHub issueStep to reproduce:
in earlier, my team using pre-commit for prettier
then we add a hooks for eslint
trying to commit a changes:
➜ web git:(xyzbranch) ✗ git commit -v -m "test"
[WARNING] Unstaged files detected.
[INFO] Stashing unstaged files to /Users/dwicao/.cache/pre-commit/patch1515120727.
[INFO] Locking pre-commit directory
just stuck at it
How to solve:
I deleted pre-commit folder at ~/.cache/
try to commit again, and it just worked flawlessly 🎉
Issue Analytics
- State:
- Created 6 years ago
- Reactions:13
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Why do I get stuck at "running pre-commit checks... running ...
The project has added a pre-commit hook, a program which runs when you try to commit something. It should be in .git/hooks/pre-commit ....
Read more >pre-commit
We built pre-commit to solve our hook issues. It is a multi-language package manager for pre-commit hooks. You specify a list of hooks...
Read more >Pre-commit model - Helix Swarm Guide (2022.2)
Create a new workspace folder using a GUID-based filename, and take a lock on the folder. Release the manage.lock lock. Perform the necessary...
Read more >Understanding Subversion repository hooks - VisualSVN
This article briefly describes Subversion repository hooks and how ... The post-lock hook runs after one or more paths have been locked.
Read more >TortoiseSVN's Settings
This reopens the commit dialog automatically at the same directory after a successful ... to write a lock message explaining why you have...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I know that this has been resolved and closed. The way to preproduce is killing the pre-commit process before finishing which doesn’t delete the lock file in ~/.cache/pre-commit/.lock .
I get this as well, on Linux. I can’t give steps to reproduce though.