{"version":"2.1.280","anchor":"snapshot-results-now-record-whether-head-moved-mid-pass-and","canonical_anchor":"snapshot-results-now-record-whether-head-moved-mid-pass-and","heading":"Snapshot results now record whether HEAD moved mid-pass and whether the index lock held throughout","tier":"internal","area":"Git Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/snapshot-results-now-record-whether-head-moved-mid-pass-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Snapshot results now record whether HEAD moved mid-pass and whether the index lock held throughout\n\nGit snapshots can now report whether HEAD moved mid-pass and whether the index lock was held throughout\n\n**What**\n\nClaude Code's snapshot function, used for git directory syncing, gained an `acceptMovedHead` option. If a caller opts in and the repository's HEAD moves while the snapshot is being taken, the snapshot now continues using the HEAD it first read instead of failing with a \"momentary\" error. The result also now reports `indexLockThroughout` (whether the index lock was held for the whole pass) and `headMovedAccepted` (whether a HEAD move was accepted).\n\n**Why**\n\nThis makes git snapshots more resilient to HEAD changing mid-snapshot when explicitly allowed, while still reporting exactly what happened so problems can be diagnosed.\n\n- Area: Git Sync\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}