{"version":"2.1.296","anchor":"git-commit-detection-from-reflog","canonical_anchor":"git-commit-detection-from-reflog","heading":"Commit detection reads git's own history log","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/git-commit-detection-from-reflog","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Commit detection reads git's own history log\n\nClaude Code's check for whether a command made a git commit reads git's own record of recent changes to find the commit and branch\n\n**What**\n\nClaude Code's check for whether a command created a git commit has changed. It reads git's own log of where the current branch has pointed, stored in `.git\/logs\/HEAD`. If the newest entry looks like a commit, including amends, merges, cherry-picks and rebases, Claude Code confirms the branch points at it. It then reports the commit ID and branch.\n\n**Why**\n\nThis lets Claude Code tell a commit was made without trying to work it out from the text of the command.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}