Reviews and checks

Reviews and checks protect the current Change Request version. A new version cannot inherit an approval or successful check by accident.

Reviews

Reviewers can approve, request changes, or leave a comment. Review requests may target a person, team, or agent and stay attached to the version that was requested.

Self-approval rules and repository permissions are enforced by the backend.

Checks

Checks can come from Actions, Kairo, or an external system. Each report has a stable check key, status, summary, and optional details and logs links.

Common states are pending, running, passed, failed, skipped, and error.

Required checks

Repository maintainers choose which check keys are required. A required check must pass on the current version before the Change Request can merge.

Actions workflows use the canonical ci/<workflow-name> check-key convention. Delivery or provider failures stay distinct from a workflow test failure.