You'll notice
Useful3 Signal1
Snapshots of your uncommitted work retry files that changed mid-copy instead of dropping them.
What's wrong with this entry?
Anonymous. No account, no email.
What
The snapshot that captures uncommitted work now makes a second staging pass over files that changed while it was copying them, instead of leaving them out on the first failure.
Details
- Files still unstable after the retry are recorded as left out with reason "unstable", alongside the existing "hardlinked" and "filtered" reasons.
- Index entries are listed so files marked skip-worktree can be told apart from files that are genuinely gone.
- Deleted-but-unstaged files are returned as their own list on the result.
- The bulk add no longer passes
--remove; deletions are handled on a separate path.
Evidence
changed while it was being read
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.233
Checkpoint notice now tells you how to undo the turn
Both mention checkpoint
-
v2.1.233
Resume checkpoint file now tells you how to undo the turn
Both mention checkpoint