PRODUCT GUIDE
Understand a run
Read outcomes, coverage, evidence, and regression feedback.
01Three outcomes
Passed means the executed checks succeeded. Failed means a checked flow found a regression. Couldn’t run means access, environment, fixture, or execution conditions prevented a conclusive result.
A healed annotation explains that a repair was used; it does not replace the pass/fail outcome. An infrastructure block produces a neutral GitHub conclusion.
02Four coverage labels
Checked: a flow was executed. Not affected: selection did not identify it as affected by this change. Inactive: the flow was not active coverage. Couldn’t run: the flow could not produce a conclusive check.
Not affected is not the same as passed. Review the selection explanation in technical details when you need to understand why coverage was selected.
03Help qualify failures
Inspect the failure explanation, screenshot, and video when available. Mark Yes, real bug or Not a real bug on the failing flow-run. Your verdict is recorded and can be corrected.
Feedback qualifies the product’s regression and false-positive reporting. It does not immediately rewrite the pull request or guarantee a model-training change.
Ready to put it into practice?
Open your workspace, or walk through setup with the founder.