{"version":"2.1.238","anchor":"cloud-file-sync-distinguishes-committed-credential-looking-f","canonical_anchor":"cloud-file-sync-distinguishes-committed-credential-looking-f","heading":"Cloud file sync distinguishes committed credential-looking files","tier":"notice","area":"Cloud Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/cloud-file-sync-distinguishes-committed-credential-looking-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Cloud file sync distinguishes committed credential-looking files\n\nCredential-looking files that are committed to git are reported separately and explained.\n\n**What**\n\nFiles whose names look like credentials but which are tracked in git are now reported separately from untracked ones, and the skip message explains that file sync never carries them while a committed version still reaches the next session through git.\n\n**Details**\n\n- Adds a `sensitive_tracked` skip reason and its own pass in the upload pipeline.\n\n**Evidence**\n\n` (file sync never carries those; a committed version reaches the next session through git)`\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}