{"version":"2.1.281","anchor":"direct-publish-upload-also-checks-filter-attributes-for-mode","canonical_anchor":"direct-publish-upload-also-checks-filter-attributes-for-mode","heading":"Direct-publish upload also checks filter attributes for mode changes and assume-unchanged mismatches","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/direct-publish-upload-also-checks-filter-attributes-for-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Direct-publish upload also checks filter attributes for mode changes and assume-unchanged mismatches\n\nThe work-in-progress upload now also checks file-mode changes and refuses on assume-unchanged or skip-worktree mismatches\n\n**Unclear.** The finding does not say what action starts the direct-publish upload.\n\n**What**\n\nThe direct-publish upload takes a snapshot of your uncommitted work and logs under `[wipStash]`. It now runs two extra checks:\n\n- `.gitattributes` is read for files whose staged file mode changed, not only for files whose content changed. `.gitattributes` is a git file that can mark paths for special processing. A file mode is a permission such as executable.\n\n- The upload refuses when a file is marked assume-unchanged or skip-worktree in one copy of the index but not the other. The index is git's record of what is staged. Those two marks tell git to stop watching a file for changes.\n\n**Why**\n\nFiles that only changed permissions are now checked the same way as edited files. The upload also stops, instead of producing a snapshot that may not match your working files, when git's bookkeeping shifted while the upload was being built."}