{"version":"2.1.282","anchor":"dir-sync-new-warning-when-gitinfoattributes-blocks-apply","canonical_anchor":"dir-sync-new-warning-when-gitinfoattributes-blocks-apply","heading":"Cloud directory sync now explains when .git\/info\/attributes blocks incoming changes","tier":"notice","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/dir-sync-new-warning-when-gitinfoattributes-blocks-apply","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Cloud directory sync now explains when .git\/info\/attributes blocks incoming changes\n\nWhen .git\/info\/attributes stops cloud changes from being applied locally, Claude Code now warns you and says to move the lines into .gitattributes\n\n**Unclear.** It is not settled whether earlier versions showed a different message when this skip happened.\n\n**What**\n\nClaude Code can sync a folder with a cloud session, keeping the files on your machine and the copy in the cloud in step. Sometimes it skips applying the cloud-side changes because of your repository's `.git\/info\/attributes` file. When that happens, it now shows a warning that those changes stayed in the cloud. The warning gives one of two reasons:\n\n- The file cannot be read as an ordinary file, for example because it is a link or is larger than 64 KiB.\n\n- The file contains a filter, encoding or macro rule that could switch off git-crypt or git-lfs.\n\nThe warning tells you to move those lines into `.gitattributes`.\n\n**Why**\n\nEdits made in the cloud could fail to reach your machine with no explanation. Now you are told why the changes did not arrive and what to change so they can.\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}