How to fix hint: The '.git/hooks/pre-commit' hook was ignored because it's not set as executable in Git

Run the chmod command to add the executable bit to your pre-commit hook:

chmod +x .git/hooks/pre-commit

If you have multiple hooks that need to be fixed:

chmod +x .git/hooks/*

This is the most common fix and works on Linux and macOS.

Check the current permissions on your hook file:

ls -la .git/hooks/pre-commit

You should see an 'x' in the permissions, like:

-rwxr-xr-x 1 user user 1234 Jan 1 12:00 pre-commit

If the file shows -rw-r--r-- (no x), it's not executable.

On Windows, the file system doesn't support Unix-style permissions. Use Git's built-in option to set the executable bit:

git add --chmod=+x .git/hooks/pre-commit

Alternatively, if you're using Git Bash, the chmod command should still work:

chmod +x .git/hooks/pre-commit

Verify which hooks directory Git is using:

git config core.hooksPath

If this returns a custom path (like .husky), make sure the hooks in that directory are executable:

chmod +x .husky/pre-commit

If core.hooksPath is not set, Git uses .git/hooks/ by default.

If you're using Husky for Git hooks, add a prepare script that ensures hooks are executable:

{
  "scripts": {
    "prepare": "husky install && chmod ug+x .husky/*"
  }
}

Then run:

npm run prepare

This ensures hooks are executable after installation on any Unix-based system.

If chmod doesn't work, your file system might be mounted with the noexec flag. Check mount options:

mount | grep $(df . --output=source | tail -1)

If you see noexec in the output, you'll need to remount the partition or work in a directory on a different file system. This is common on:
- Dual-boot systems with NTFS partitions
- Mounted network drives
- Some Docker volume mounts

If you intentionally want hooks to be non-executable (to disable them), you can suppress the warning:

git config advice.ignoredHook false

Note: This only hides the warning. If you actually want the hooks to run, fix the permissions instead.