You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Git SafetyArea: what it touches
ImprovementsKind: in v2.1.247,
ImprovementsSection of the release
What
Creating or reusing a worktree for an agent now blanks every filter driver the repository config defines, so checking out files cannot run programs the repo supplies. Three situations stop worktree creation instead: git config that cannot be read, a filter whose name contains = or a newline, and a config using a conditional include. This is active in this build with no flag.
Details
The repository's local and per-worktree config is read with --includes and -z --list, and for each filter driver found the git call gets -c filter.<name>.clean=, .smudge=, .process= and .required=false.
Each refusal records its own telemetry: git_worktree_create_config_unreadable, git_worktree_create_filter_name_unrepresentable, git_worktree_create_conditional_include.
A conditional include is refused because the set of filters a checkout would load cannot be worked out ahead of time.
Evidence
The repository git config has a conditional include (includeIf), so the filter drivers a checkout would load cannot be determined
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
