{"version":"2.1.242","anchor":"secrets-in-commits-now-block-sync-not-just-uploads","canonical_anchor":"secrets-in-commits-now-block-sync-not-just-uploads","heading":"Secrets in commits now block sync, not just uploads","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/secrets-in-commits-now-block-sync-not-just-uploads","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Secrets in commits now block sync, not just uploads\n\nSync now refuses to carry commits containing credential-looking or Read-denied files.\n\n**What**\n\nBefore taking a snapshot, sync scans the commits the cloud session has not seen yet. If any of them contain files whose names look like credentials, or that your Read permission rules deny, sync refuses to carry those commits and tells you that deleting the file in a later commit does not fix it.\n\n**Details**\n\n- Staged files matching the same rules also stop the snapshot, with advice to unstage rather than commit.\n- The remedy given is to amend or reset the offending commits.\n- Paths held back are listed back to you as \"Left on this machine, not synced\".\n\n**Evidence**\n\n`amend or reset the commits (deleting the file in a later commit is not enough)`\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}