Unverified50% confidenceFactExact time
When the path pointed to by core.hooksPath exists but the executable file is missing or lacks execute permission, Git treats it as having no hooks and silently continues the commit.
1
Sources
50%
Confidence
Long-term
Relevance
10/16/2026
First Seen
Sources
Related Entities
Related Claims
Unverified~/.config/git/ignore is the default lookup path for Git 2.x and takes effect even without explicitly configuring core.excludesFile77% similarUnverifiedA configured hook path only says where Git will look, not whether there is an executable file there.74% similarUnverifiedCreating a new git worktree inherits the main checkout's core.hooksPath configuration, but does not automatically generate the executable shims under .husky/_, causing Husky hooks to silently fail while commits still succeed.72% similarUnverifiedGit provides three ignore files: the project-level .gitignore, the global core.excludesFile, and the local .git/info/exclude71% similarVerifiedThe Git protocol itself is highly stateful, as repository read and write operations require access to specific storage nodes, making simple horizontal scaling inapplicable to the core Git service layer.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1044737API
curl https://kongchang.com/api/v1/knowledge/claims/1044737MCP
get_claim(id=1044737)