You'll notice
Useful3 Signal2
Sync pulls set your local file aside in a trash directory instead of overwriting it.
What's wrong with this entry?
Anonymous. No account, no email.
What
When a sync pull would replace a local file, it is now set aside in a trash directory rather than clobbered, and the sync record tracks what was set aside so it is not fetched again. A new warning also tells you when a file was withheld because a git content filter such as LFS or git-crypt stores it.
Details
- The pull call takes a trash directory and a set-aside callback; results now report files kept, kept under a path, and replaced without copying.
- The stored sync base gains a tombstone block covering published, withheld, pending and judged entries, each with its own size cap.
- Entries already marked as trashed are treated as resolved instead of re-downloaded.
- No feature flag was found on this path.
Evidence
git stores
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