devpit
Expanding a run opens what it proves. The panel states three separate facts, in words rather than in colour: what the check said, whether it is still about the code in front of you, and what it found. "Green" is exactly the answer this exists to stop being given for free.
Verdict
| Word | What it means |
|---|---|
| Passed | A report was read and everything in it passed. |
| Failed | A report was read and something in it failed. |
| Not run | This check never happened. |
| No result | It ran and left nothing devpit can read as a result. Exit code zero is not a pass. |
No result is the common one, and it is deliberate. A runner that matched no test files exits zero and checked nothing, so exit zero on its own is never read as a pass. The one report devpit reads today is a review — an agent answer that comes back as findings — so a command step that exits zero reports No result rather than a green tick, and a run that is still going, or that you stopped, reports Not run.
Validity
| Word | What it means |
|---|---|
| Current | The commit and the uncommitted work are the ones it saw. |
| Stale | The code moved since. This is about what was there then. |
| Unknown | Nothing recorded what this run saw, so nothing can say whether it still holds. |
Current means the same commit and the same uncommitted work — not the same machine.
Findings
A review's findings are listed with their severity, the file and line, and the reason. The panel also shows what the review was asked to look for, and says "This review found nothing it was asked to look for." when one ran clean — which is a different sentence from having found nothing to say.
Who, and what ran
Two sentences, because they are two facts: who asked for the run — a card moving into a lane, the card's own play, the lane before it passing the card on, or a run started from Checks itself — and what carried it out, a command devpit started on this machine or an agent session, with the profile named when there was one.
Below that is what ran: the command, the folder, whether it was this card's own
checkout, the git revisions, and the names of the environment variables it was
given — names only, never values. Those are recorded before the command starts,
because a step that commits would otherwise move HEAD out from under its own
snapshot.
There is also a preview of what running it again would do, which runs nothing.