{"version":"2.1.248","anchor":"work-in-progress-stash-snapshots-restage-files-that-moved-mi","canonical_anchor":"work-in-progress-stash-snapshots-restage-files-that-moved-mi","heading":"Work-in-progress stash snapshots restage files that moved mid-copy","tier":"notice","area":"Checkpoints","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/work-in-progress-stash-snapshots-restage-files-that-moved-mi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Work-in-progress stash snapshots restage files that moved mid-copy\n\nSnapshots of your uncommitted work retry files that changed mid-copy instead of dropping them.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- Files still unstable after the retry are recorded as left out with reason \"unstable\", alongside the existing \"hardlinked\" and \"filtered\" reasons.\n- Index entries are listed so files marked skip-worktree can be told apart from files that are genuinely gone.\n- Deleted-but-unstaged files are returned as their own list on the result.\n- The bulk add no longer passes `--remove`; deletions are handled on a separate path.\n\n**Evidence**\n\n`changed while it was being read`\n\n- Area: Checkpoints\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}