What
Cloud 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.
Details
- The stop is recorded with the reason
linked_worktree, and is handled the same way as a.gitfile that could not be verified, replacing the previous behaviour of probing the work tree. - Sync reports that
a linked working tree is not fast-forwarded yetin place of the older git directory wording. - 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.
Evidence
a linked working tree (directory sync does not run its own git in one yet), a linked working tree is not fast-forwarded yet
Strings lifted out of the shipped bundle, so the claim above can be checked against them.