Cloud review now tells you to create a branch when your checkout has none.
What's wrong with this entry?
If your checkout has no branches at all, cloud review now says so and tells you to create one with git checkout -b <name> before rerunning, instead of falling into the generic "no refs" message.
Your checkout has no branches (detached HEAD only), which cloud review can't bundle. Create one first \u2014 \git checkout -b <name>\ \u2014 then rerun
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