{"version":"2.1.277","anchor":"curious-no-op-looking-then-inserted-into-worktree-detecti","canonical_anchor":"curious-no-op-looking-then-inserted-into-worktree-detecti","heading":"Curious no-op-looking .then() inserted into worktree detection telemetry chain","tier":"internal","area":"Git Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/curious-no-op-looking-then-inserted-into-worktree-detecti","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Curious no-op-looking .then() inserted into worktree detection telemetry chain\n\nAn extra pass-through step was added to the internal chain that reports git worktree detection timing\n\n**Unclear.** The extra step returns its input unchanged, so it's unclear what purpose it serves or whether it has any visible effect.\n\n**What**\n\nThe internal code path that measures how long git worktree detection takes (worktrees let you check out multiple branches of a repo at once) now runs one extra step before reporting the `tengu_worktree_detection` timing telemetry. This step reads the length of a list of results and then passes the list along unchanged.\n\n**Why**\n\nThe step doesn't appear to alter the data, so this looks like an internal adjustment to how the timing is measured or logged rather than a change to worktree detection itself. It's not clear yet what purpose the extra step serves.\n\n- Area: Git Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}