{"version":"2.1.281","anchor":"cloud-file-sync-snapshot-reads-committed-gitattributes-from","canonical_anchor":"cloud-file-sync-snapshot-reads-committed-gitattributes-from","heading":"Cloud file-sync snapshot reads committed .gitattributes from more sources","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-file-sync-snapshot-reads-committed-gitattributes-from","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud file-sync snapshot reads committed .gitattributes from more sources\n\nCloud file sync now reads committed `.gitattributes` from extra commits or trees and reports more reasons a sync was not applied\n\n**Unclear.** The finding does not say what folding your machine's installs into the agreed tree changes for a user.\n\n**What**\n\nThis concerns syncing files between your machine and a cloud session. `.gitattributes` is a git file that sets rules for particular paths. The sync snapshot changes as follows:\n\n- It can take extra `attributeSources`, each a commit or a tree (a saved folder state in git), and caches those attribute trees in its sync repository.\n\n- It reports `attributesTrees` and `attributesNotKept`, with the reason given as gone, overflow or missing.\n\n- It has several new error messages, such as \"could not read back what the cloud session was last sent for the files kept on this machine\".\n\n- Paths held at the state last sent to the cloud are now also protected when files or directories are moved.\n\n- Sync results can report two new reasons for not being installed: \"deferred\" and \"stale_basis\".\n\n- Installs from your machine are folded into the tree both sides agree on.\n\n**Why**\n\nThe cloud side can respect more of your committed `.gitattributes` rules. When a sync is not applied, or something could not be read back, the report now says more precisely why."}