{"version":"2.1.248","anchor":"directory-sync-skips-the-merge-when-both-sides-already-match","canonical_anchor":"directory-sync-skips-the-merge-when-both-sides-already-match","heading":"Directory sync skips the merge when both sides already match","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/directory-sync-skips-the-merge-when-both-sides-already-match","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Directory sync skips the merge when both sides already match\n\nDirectory sync skips the merge entirely when local and remote already match.\n\n**What**\n\nSyncing a directory now reads the three git snapshots it compares in one go and, when the local and remote trees are identical, produces a clean result without running a merge at all.\n\n**Details**\n\n- Failure to read the snapshots now reports \"could not read the HEAD or laptop snapshot trees\" instead of naming a single tree.\n- A merge-base failure returns a structured git error saying \"could not wrap the merge base\" rather than aborting the whole sync plan.\n\n**Evidence**\n\n`could not read the HEAD or laptop snapshot trees`\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}