{"version":"2.1.238","anchor":"sync-asks-git-s-clean-filter-before-re-uploading-stat-dirty-","canonical_anchor":"sync-asks-git-s-clean-filter-before-re-uploading-stat-dirty-","heading":"Sync asks git's clean filter before re-uploading stat-dirty files","tier":"notice","area":"Cloud Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/sync-asks-git-s-clean-filter-before-re-uploading-stat-dirty-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Sync asks git's clean filter before re-uploading stat-dirty files\n\nFiles that only look changed by timestamp are checked against git's clean filter, avoiding re-uploads.\n\n**What**\n\nA file whose timestamp says it changed but whose git blob id says otherwise is now run through git's clean filter, and treated as unchanged if the filter agrees. Fewer spurious re-uploads of files that a clean filter rewrites on checkout.\n\n**Details**\n\n- A debug line reports how many files were asked and how many the filter answered for.\n\n**Evidence**\n\n`arming asked git's clean filter about`\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}