You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
GitArea: what it touches
ImprovementsKind: in v2.1.285,
ImprovementsSection of the release
What
Claude 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:
an include, which pulls settings in from another file
a core.worktree setting
a configuration file it cannot read
a shared second name
the worktreeConfig setting
The 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.
Why
More 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.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear where this check runs, what happens when it flags something, or what the shared second name case covers.