Unverified50% confidenceFactExact time
Creating 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.
1
Sources
50%
Confidence
Long-term
Relevance
10/16/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen 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.72% similarUnverifiedawman uses Git's git worktree feature to implement isolated work trees, preventing conflicts when multiple agents modify code in parallel.67% similarUnverifiedWhen you manually run git worktree add yourself, or mix Agents from different vendors, the .worktreeinclude mechanism will not trigger; and the port issue must be solved by you on all paths.65% similarUnverifiedGit Worktree方案不复制对象数据库，磁盘占用极低，创建新Worktree几乎是瞬时操作64% similarUnverifiedGit worktree itself does not provide task assignment, agent monitoring, or automatic conflict resolution, and still requires manually managing sessions and tracking progress.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1044736API
curl https://kongchang.com/api/v1/knowledge/claims/1044736MCP
get_claim(id=1044736)