{"version":"2.1.281","anchor":"cloud-file-sync-notices-for-credential-named-files-already","canonical_anchor":"cloud-file-sync-notices-for-credential-named-files-already","heading":"Cloud file sync: notices for credential-named files already on origin and for cloud file names this machine cannot write","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-file-sync-notices-for-credential-named-files-already","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud file sync: notices for credential-named files already on origin and for cloud file names this machine cannot write\n\nCloud file sync now reports credential-named files already on origin and cloud file names it cannot write locally\n\n**What**\n\nWhen your project is synced with a cloud session, two new messages can appear after an upload:\n\n- A note listing files with credential-like names in new commits that are already on origin (the shared remote repository), so they are carried along with the upload.\n\n- A warning listing files in the cloud session whose names are not valid text (UTF-8) or clash with another name on your machine, so they are not brought down.\n\nThe \"Left on this machine, not synced:\" list also gains a new category, `hostConfig`.\n\n**Why**\n\nYou can see when sensitive-looking files travel because they were already shared, and which cloud files did not reach your machine.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}