{"version":"2.1.212","anchor":"ultrareview-auto-fetches-missing-branches","canonical_anchor":"ultrareview-auto-fetches-missing-branches","heading":"Ultrareview Auto-Fetches Missing Branches","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.212\/e\/ultrareview-auto-fetches-missing-branches","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.212","markdown":"### Ultrareview Auto-Fetches Missing Branches\n\nWhen `\/code-review ultra` or `\/review` can't find the specified base branch, it now attempts to auto-fetch it from origin before failing. If fetch succeeds, the review proceeds without user intervention.\n\n**Details**\n\n- Uses `git ls-remote --heads origin <branch>` to check existence, then `git fetch ... refs\/heads\/<branch>:refs\/remotes\/origin\/<branch>`.\n- If the branch exists on origin but couldn't be fetched: `\"<branch>\" exists on origin but couldn't be fetched. Run \\`git fetch origin <branch>\\` and try again.`\n- If the branch name looks like a typo, Claude now suggests the closest branch: `\"<name>\" is not a branch in this repo. Did you mean \\`<suggestion>\\`?`\n- Shallow clone detection: if fetch succeeds but no merge-base exists, suggests `git fetch --unshallow origin`.\n\n**Evidence**\n\n`\"exists on origin but couldn't be fetched. Run \\`git fetch origin\"` (search for `\"JI_\"`)"}