{"version":"2.1.285","anchor":"git-config-safety-check-covers-configworktree-includes-and","canonical_anchor":"git-config-safety-check-covers-configworktree-includes-and","heading":"Git configuration safety check reads more files and settings","tier":"notice","area":"Git","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/git-config-safety-check-covers-configworktree-includes-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Git configuration safety check reads more files and settings\n\nA git configuration safety check now reads config.worktree as well as config, and flags includes, core.worktree and unreadable files\n\n**Unclear.** It is not clear where this check runs, what happens when it flags something, or what the shared second name case covers.\n\n**What**\n\nClaude Code runs a safety check on a git repository's configuration files. This check now reads the per-worktree file, config.worktree, as well as the main config file. A worktree is an extra working copy of the same repository. The check now flags:\n\n- an include, which pulls settings in from another file\n\n- a core.worktree setting\n\n- a configuration file it cannot read\n\n- a shared second name\n\n- the worktreeConfig setting\n\nThe way it handles git hook configuration keys has also changed. Git hooks are scripts that git runs on its own at certain moments, such as before a commit.\n\n**Why**\n\nMore of a repository's configuration is now looked at. A setting placed in a worktree file or pulled in through an include is less likely to slip past the decisions Claude Code makes about permissions and its sandbox, the restricted area it runs commands in.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}