{"version":"2.1.247","anchor":"directory-sync-detects-linked-worktrees-and-declines-to-run-","canonical_anchor":"directory-sync-detects-linked-worktrees-and-declines-to-run-","heading":"Directory sync detects linked worktrees and declines to run git in them","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/directory-sync-detects-linked-worktrees-and-declines-to-run-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Directory sync detects linked worktrees and declines to run git in them\n\nDirectory sync now detects a linked worktree and says so instead of a misleading git-directory message.\n\n**What**\n\nCloud directory sync now checks whether the folder it is syncing is a linked working tree, a checkout whose `.git` is a file pointing back at a main repository rather than a real git directory. In that case it stops rather than probing inside the work tree, and says so directly instead of falling back to the misleading message about the git directory not being where git keeps it. Anyone whose checkout has that shape hits this on this build.\n\n**Details**\n\n- The stop is recorded with the reason `linked_worktree`, and is handled the same way as a `.git` file that could not be verified, replacing the previous behaviour of probing the work tree.\n- Sync reports that `a linked working tree is not fast-forwarded yet` in place of the older git directory wording.\n- Snapshotting uses its own phrasing for the same case, noting that directory sync does not run its own git in a linked working tree yet.\n\n**Evidence**\n\n`a linked working tree (directory sync does not run its own git in one yet)`, `a linked working tree is not fast-forwarded yet`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}