{"version":"2.1.305","anchor":"base-branch-for-review-resolves-as-fetch-head-only","canonical_anchor":"base-branch-for-review-resolves-as-fetch-head-only","heading":"Review base branch is always treated as coming from the last fetch","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/base-branch-for-review-resolves-as-fetch-head-only","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Review base branch is always treated as coming from the last fetch\n\nWhen Claude Code works out which branch to compare against for a review, it now always labels it as the last fetched commit\n\n**Unclear.** How this changes which commits a review compares against is not known.\n\n**What**\n\nWhen Claude Code works out the base branch for a review, the point your changes are compared against, it now always marks the result as coming from the last fetch, Git's `FETCH_HEAD`. Before, it marked it as the remote's default branch whenever the base was not `FETCH_HEAD`.\n\n**Why**\n\nThis could change how Claude Code finds the starting point for a diff.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}