dánwòdánwò

Running

Pull request comment

One comment on each pull request, edited by every run, with each test, each failure and what the matrix found.

On a pull request, danwo's GitHub reporter posts one comment and edits it on every later run. The conversation never fills with copies, and the comment always shows the latest commit.

Turn it on

It's on whenever the GitHub reporter runs on a pull_request event and the token may write to pull requests:

npx @danwo/cli test --reporter github

The workflow needs pull-requests: write. See CI and GitHub.

What it shows

PartWhat's in it
the headlinepassed, failed, flaky and not judged; duration, model spend and commit
a row per testits duration and retries, failures first
each failurefolded: the failing step, the error and its class, the last provider calls and any faults in them, its flight record
flaky testsfolded away
each matrix testwhether its invariant held under every fault, and a row per fault that broke it

Set DANWO_REPORT_URL to where you publish the report or dashboard, and each test name links there.

How runs share it

  • A run replaces its own section and keeps the others for the same commit. A danwo test run and a danwo matrix run both show.
  • A section from an older commit is dropped.
  • A shard leaves the comment alone; danwo merge-reports posts the whole run once.
  • The comment stays under GitHub's size limit. A long one is cut between entries, with a note.

Turn it off

WayScope
--no-pr-commentone command
DANWO_PR_COMMENT=offthe job
github({ prComment: false }) in reportersthe project

The check run stays either way.

Next

On this page

Run it on every pull request

A GitHub check and one comment per pull request, with the flight records attached.

Set up CI