-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Description
I've set up a pre-merge-commit hook using Husky, but it doesn't seem to be triggering when I perform a merge. Here are the details:
Steps to Reproduce:
- Add a pre-merge-commit hook with the following command:
echo "echo 'pre-merge-commit hook triggered'" > .husky/pre-merge-commit- Merge a branch that should trigger the pre-merge-commit hook.
- Notice that the hook does not run.
Expected Behavior:
The pre-merge-commit hook should trigger and display the message pre-merge-commit hook triggered before the merge is completed.
Actual Behavior:
The pre-merge-commit hook is not triggered at all, and the merge process continues without any output from the hook.
Environment:
Husky Version: ^9.1.4
Node Version: 20.8.0
Git Version: 2.46.0
Operating System: MacOS Sonoma 14.0
Additional Context:
Workaround
There is a workaround to fix this issue by manually adding a pre-merge-commit file in the ./husky/_ directory with the following content:
#!/usr/bin/env sh
. "$(dirname "$0")/h"After ensuring the file is executable, the issue is resolved. However, when the _ directory is deleted and Husky is re-initialized using the npm run prepare command, the pre-merge-commit file is not generated. This defeats the purpose of using Husky, as the hook needs to be manually recreated each time.