You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
CheckpointsArea: what it touches
ImprovementsKind: in v2.1.248,
ImprovementsSection of the release
What
When a checkpoint snapshot fails because files were changing underneath it, that is now reported as a momentary failure rather than as a corrupt attributes file or an unreadable path, so a retry is the obvious response.
Details
Three cases now produce the momentary result: staged copies changing while git read them, .git/info/attributes changing mid-read, and the staging step itself reporting momentary.
momentary is carried through as its own reason code next to too_large, busy and too_many_paths.
A file that changes while being read gets an explicit message naming that file.
No such classification existed in the previous build.
Evidence
the staged copies changed while git read them
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
