Code review findings now carry a short claim and a category like correctness or efficiency.
What's wrong with this entry?
Each finding in a code review must now include a one-line claim of at most 60 characters with no rationale, plus a category slug such as correctness, simplification, efficiency, reuse, altitude or conventions, alongside the existing file, line, summary and failure scenario.
- The review is also forbidden from printing the same findings as plain text or publishing them as a separate artifact.
the claim compressed to ≤60 characters, no rationale
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.221
Cloud review: better messages for detached HEAD and wrong base branch
Both mention code review