{"version":"2.1.282","anchor":"cloud-file-sync-skips-a-round-when-gitinfoattributes-is-u","canonical_anchor":"cloud-file-sync-skips-a-round-when-gitinfoattributes-is-u","heading":"Cloud file sync holds back changes when .git\/info\/attributes looks unsafe","tier":"notice","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/cloud-file-sync-skips-a-round-when-gitinfoattributes-is-u","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Cloud file sync holds back changes when .git\/info\/attributes looks unsafe\n\nFiles Claude changed in a cloud session are not applied locally when .git\/info\/attributes can't be read normally or could switch off git-crypt or git-lfs\n\n**Unclear.** It is not clear which sync paths use this check, or whether it is switched on for everyone.\n\n**What**\n\nWhen Claude works in a cloud session, Claude Code can copy the files it changed back onto your machine. Your project's `.git\/info\/attributes` file is a git settings file that says how particular files are handled. Claude Code now skips copying the changed files for that round if this file:\n\n- cannot be read as a regular file\n\n- holds rules that could switch off content filters such as git-crypt or git-lfs, which change file contents as git stores and restores them\n\nThe changed files stay in the cloud session, and a warning explains how to fix the problem.\n\n**Why**\n\nWithout this check, sync could write plain, unfiltered content over files that git-crypt or git-lfs is meant to handle.\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}