Appearance
Accept results
Check the delivered work against your criteria and record your verdict.
You need: a ticket whose latest summary says the work is ready, with its merge request linked.
Read the result. Start with the
summary, then thereviewcomment: each criterion with PASS or FAIL and the evidence behind it.Check it yourself. Try the walkthrough where the summary offers one. Or ask your agent:
textRead <identifier> as bb-workflow's references/read-ticket.md describes and walk me through the review, criterion by criterion.A criterion counts when you can repeat its evidence.
Record your verdict in the browser. Add yourself under Reviewers in the ticket's Properties panel. The Reviews section then offers Write a review: describe what you checked, Submit review, then Accept or Reject. Only the decisions you are allowed to make are offered.
When you reject, name each open criterion and its cause:
Cause Meaning Next implementationthe change falls short back to workingevidencethe change may work, but nothing shows it back to workingcriterionthe criterion cannot be met as written you decide on a rewrite Requirement changed? Ask your agent to use
bb-scope-change.Merge on purpose. You authorize review, merge and deployment separately; a verdict authorizes none of them. bakers.build merges only with a linked merge request, a green pipeline and a clean merge, then moves the ticket to
done. Deployment is its own ticket.Close. At
doneorcancelledyou may give an optional rating from 1 to 5.
Done when: the ticket is done and holds your decision and its evidence.