{"version":"2.1.280","anchor":"git-sync-now-explains-more-precisely-why-previously-staged-c","canonical_anchor":"git-sync-now-explains-more-precisely-why-previously-staged-c","heading":"Git-sync now explains more precisely why previously-staged changes were dropped","tier":"notice","area":"Git Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/git-sync-now-explains-more-precisely-why-previously-staged-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Git-sync now explains more precisely why previously-staged changes were dropped\n\nGit-sync now gives a more specific reason when your earlier staged changes are no longer there\n\n**What**\n\nWhen Claude Code's git-sync feature finds that changes it had previously staged are no longer in the index, it now explains more precisely why. The message now distinguishes between three cases:\n\n- the file is gone entirely\n\n- the file's contents have changed since, in which case Claude is told to re-read it\n\n- the contents are unchanged\n\nPreviously the message always said the file contents were unchanged, even when that wasn't true.\n\n**Why**\n\nA more accurate explanation helps Claude respond correctly when its staged work disappears: it knows whether to re-read a changed file before continuing, rather than assuming nothing had changed.\n\n- Area: Git Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}