Unclear The finding does not say what action starts the direct-publish upload.
What
The direct-publish upload takes a snapshot of your uncommitted work and logs under [wipStash]. It now runs two extra checks:
.gitattributesis read for files whose staged file mode changed, not only for files whose content changed..gitattributesis a git file that can mark paths for special processing. A file mode is a permission such as executable.- 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.
Why
Files 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.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding does not say what action starts the direct-publish upload.