{"version":"2.1.300","anchor":"git-operation-in-progress-check-now-verifies-cherry-pick-hea","canonical_anchor":"git-operation-in-progress-check-now-verifies-cherry-pick-hea","heading":"Leftover git files no longer make Claude Code think an operation is running","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/git-operation-in-progress-check-now-verifies-cherry-pick-hea","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Leftover git files no longer make Claude Code think an operation is running\n\nClaude Code now checks with git before treating a leftover cherry-pick, revert or rebase marker file as an operation in progress\n\n**What**\n\nClaude Code checks whether a git operation such as a merge, rebase, cherry-pick or revert is in progress. Before this release, the mere presence of git's marker files `CHERRY_PICK_HEAD`, `REVERT_HEAD` or `REBASE_HEAD` counted as proof. Now Claude Code runs `git show-ref --exists` to confirm those references are real, and only reports an operation in progress if one is.\n\nA merge marker, and a rebase marker together with git's rebase folder, still count straight away.\n\n**Why**\n\nAfter an aborted cherry-pick or revert, git can leave a stale marker file behind. Claude Code is now less likely to wrongly say a git operation is in progress because of one.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}