What's wrong with this entry?
Anonymous. No account, no email.
When /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.
Details
- Uses
git ls-remote --heads origin <branch>to check existence, thengit fetch ... refs/heads/<branch>:refs/remotes/origin/<branch>. - 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. - 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>\? - Shallow clone detection: if fetch succeeds but no merge-base exists, suggests
git fetch --unshallow origin.
Evidence
"exists on origin but couldn't be fetched. Run \git fetch origin" (search for "JI_"`)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.