Claude Code v2.1.222 ·
Worktree git commands run with a scrubbed git environment
Stray git environment variables in your shell can no longer misdirect worktree operations.
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
WorktreesArea: what it touches
ImprovementsKind: in v2.1.222,
ImprovementsSection of the release
What
Worktree plumbing no longer inherits ambient git environment variables, so a stray GIT_DIR or a repo fsmonitor cannot redirect worktree operations.
Details
- covers create, remove, lock, status, reset, rev-parse and sparse-checkout
- blanks GIT_DIR, GIT_WORK_TREE, GIT_INDEX_FILE, GIT_CONFIG_COUNT, GIT_CONFIG_PARAMETERS, the per-index GIT_CONFIG_KEY_n and GIT_CONFIG_VALUE_n pairs, and more
- all calls go through the shared
-c core.hooksPath=/dev/null -c core.fsmonitor= prefix
Evidence
GIT_ALTERNATE_OBJECT_DIRECTORIES: void 0
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.222 →
