{"version":"2.1.301","anchor":"git-operation-in-progress-check-returns-null-when-unknown","canonical_anchor":"git-operation-in-progress-check-returns-null-when-unknown","heading":"Unreadable git state no longer counts as a cherry-pick or revert in progress","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/git-operation-in-progress-check-returns-null-when-unknown","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Unreadable git state no longer counts as a cherry-pick or revert in progress\n\nWhen Claude Code cannot tell whether a git cherry-pick or revert is underway, it now treats the answer as unknown instead of yes\n\n**What**\n\nClaude Code checks whether a git cherry-pick or revert is in progress in your repository. When it could not read that state, it used to assume one was in progress. It now records the answer as unknown instead.\n\n**Why**\n\nThis avoids Claude Code wrongly believing a cherry-pick or revert is underway just because it could not read the repository's state.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}