{"version":"2.1.300","anchor":"git-reftable-support-in-branch-and-head-watcher","canonical_anchor":"git-reftable-support-in-branch-and-head-watcher","heading":"Branch and commit tracking now works in git reftable repositories","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/git-reftable-support-in-branch-and-head-watcher","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Branch and commit tracking now works in git reftable repositories\n\nClaude Code's git watcher now recognises repositories using the reftable format, so branch and commit changes are picked up there\n\n**What**\n\nClaude Code keeps an eye on your git repository so it can show the current branch and notice new commits. Git can store its branch information in an older file layout or in a newer format called reftable. The watcher now handles reftable repositories:\n\n- It detects whether a repository uses reftable and, if so, watches `reftable\/tables.list` instead of the `HEAD` or branch files.\n\n- It records the newest reftable entry as `reftableNewest` instead of measuring the size of the usual branch file.\n\n- It avoids running the same check twice at once, and retries when reading the branch information gives an unclear answer.\n\n- Working out the current branch now handles a placeholder `HEAD` by asking `git symbolic-ref`.\n\n- Commit detection falls back to `git log --walk-reflogs` when a reftable repository has no `logs\/HEAD` file.\n\nBefore, the watcher only looked at `HEAD`, the git config and the branch file, and reftable repositories fell through to the older size check.\n\n**Why**\n\nIf your repository uses reftable, the branch shown by Claude Code and its detection of new commits should now keep up with changes instead of going stale.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}