Cloud review now tells you to create a branch on detached HEAD instead of failing with a vague error.
What's wrong with this entry?
Cloud review failures on a checkout with no branches now return a dedicated no_merge_base error telling you to create a branch first, and the "shares no history with HEAD" message suggests passing the real base branch explicitly.
- detached-HEAD checkouts previously fell through to a generic bundling failure
- the no-shared-history path now names the likely cause rather than only reporting it
Your checkout has no branches (detached HEAD only), which cloud review can't bundle.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.219
PR-review anchor repo names reject "." and ".."
Both mention code review
-
v2.1.219
Composed PR-review publish refusal explains whether it is a live switch
Both mention code review
-
v2.1.239
Code review findings now carry a short summary and a category
Both mention code review