Sync now refuses to carry commits containing credential-looking or Read-denied files.
What's wrong with this entry?
Before 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.
- Staged files matching the same rules also stop the snapshot, with advice to unstage rather than commit.
- The remedy given is to amend or reset the offending commits.
- Paths held back are listed back to you as "Left on this machine, not synced".
amend or reset the commits (deleting the file in a later commit is not enough)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.238
Sync state machine gains a moved-root case and a per-turn pull hook
Both mention directory
-
v2.1.238
Untracked-file survey extracted and shared
Both mention directory
-
v2.1.238
Sync internals reshaped around per-file credential state
Both mention directory