{"version":"2.1.281","anchor":"git-config-filter-can-drop-corehookspath","canonical_anchor":"git-config-filter-can-drop-corehookspath","heading":"Git config filter can drop core.hooksPath","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/git-config-filter-can-drop-corehookspath","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Git config filter can drop core.hooksPath\n\nA new helper can remove the `core.hooksPath` setting from a git configuration list in Claude Code's git and worktree support\n\n**Unclear.** The finding does not say when the helper is asked to drop `core.hooksPath` or which git operations use it.\n\n**What**\n\nClaude Code's git and worktree support code has a new helper that can take a list of git configuration settings and remove `core.hooksPath` from it. A worktree is a second working copy of the same git repository. `core.hooksPath` is the git setting that tells git which folder holds its hook scripts, which are scripts git runs automatically at certain moments such as before a commit.\n\nThe helper removes the setting only when it is asked to. Otherwise it returns the list unchanged.\n\n**Why**\n\nIn practice, some git configuration that Claude Code passes along can now leave out the pointer to a custom hooks folder."}