{"version":"2.1.239","anchor":"directory-sync-moves-files-aside-instead-of-overwriting-them","canonical_anchor":"directory-sync-moves-files-aside-instead-of-overwriting-them","heading":"Directory sync moves files aside instead of overwriting them","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/directory-sync-moves-files-aside-instead-of-overwriting-them","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Directory sync moves files aside instead of overwriting them\n\nSync pulls set your local file aside in a trash directory instead of overwriting it.\n\n**What**\n\nWhen a sync pull would replace a local file, it is now set aside in a trash directory rather than clobbered, and the sync record tracks what was set aside so it is not fetched again. A new warning also tells you when a file was withheld because a git content filter such as LFS or git-crypt stores it.\n\n**Details**\n\n- The pull call takes a trash directory and a set-aside callback; results now report files kept, kept under a path, and replaced without copying.\n- The stored sync base gains a tombstone block covering published, withheld, pending and judged entries, each with its own size cap.\n- Entries already marked as trashed are treated as resolved instead of re-downloaded.\n- No feature flag was found on this path.\n\n**Evidence**\n\n`git stores `\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}