{"version":"2.1.238","anchor":"directory-sync-notices-when-the-checkout-has-moved","canonical_anchor":"directory-sync-notices-when-the-checkout-has-moved","heading":"Directory sync notices when the checkout has moved","tier":"notice","area":"Cloud Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/directory-sync-notices-when-the-checkout-has-moved","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Directory sync notices when the checkout has moved\n\nIf your checkout moves mid-sync, the sync aborts instead of writing into the wrong tree.\n\n**What**\n\nSync now records the directory it resolved at the start and compares it against the current real path before applying anything. If they differ, the apply aborts with `root_moved` instead of writing into the wrong tree.\n\n**Details**\n\n- A restarted sync worker re-hashes the files it had already seeded against the new location rather than trusting the old hashes.\n- Startup decides whether the sync prompt is worth offering at all, and prints a dimmed status line while it works that out.\n- Files refused as credentials during apply are counted separately.\n\n**Evidence**\n\n`Checking whether this checkout can sync`\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}