{"version":"2.1.287","anchor":"git-operation-in-progress-detection-includes-rebases","canonical_anchor":"git-operation-in-progress-detection-includes-rebases","heading":"Claude Code now notices a git rebase that is still in progress","tier":"notice","area":"Git","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/git-operation-in-progress-detection-includes-rebases","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Claude Code now notices a git rebase that is still in progress\n\nThe check for an unfinished git operation now also recognises a rebase in progress, not only merges, cherry-picks and reverts\n\n**What**\n\nClaude Code checks whether your git repository is in the middle of an operation that has not finished. That check used to look only for the marker files git leaves during a merge, rebase, cherry-pick or revert. It now also looks for the `rebase-merge` and `rebase-apply` folders, which git creates while a rebase (replaying your commits on top of another branch) is under way.\n\n**Why**\n\nA rebase that is still in progress is now reported more reliably, so Claude Code is less likely to treat the repository as idle while one is half done.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}