{"version":"2.1.281","anchor":"directory-sync-new-messages-for-commits-set-aside-or-restor","canonical_anchor":"directory-sync-new-messages-for-commits-set-aside-or-restor","heading":"Directory sync: new messages for commits set aside or restored","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/directory-sync-new-messages-for-commits-set-aside-or-restor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Directory sync: new messages for commits set aside or restored\n\nDirectory sync now tells you what happened to Claude's commits and why a file was not installed\n\n**What**\n\nClaude Code has a new report that explains, in plain messages, what happened to the commits Claude made while syncing a directory. A commit is a saved snapshot of changes in a git repository. The report covers these cases:\n\n- Commits set aside after a branch switch\n\n- Commits that a remote copy of the repository already has\n\n- Rewritten commits that were restored\n\n- Lines that were edited on both sides, where your lines won and Claude was told what it lost\n\n- A folder replaced by a file, or a file replaced by a folder\n\nIt also gives reasons when a file was not installed, such as the file having a credential-like name, being too large, or being excluded by a filter attribute.\n\n**Why**\n\nWhen your work and Claude's work meet, you can now see which of Claude's changes were kept, set aside or dropped, and why a particular file did not come across.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}