One step in the workflow
Add @kinora/reporter to playwright.config and put KINORA_TOKEN in the job env. No artifact upload, no extra step, no change to your tests.
[ GitHub Actions ]
Playwright reports for GitHub Actions
Add the reporter to your workflow and every GitHub Actions run lands in kinora with its commit, branch, and run link. Pull requests get a summary comment, and the trace for any failure opens in the browser.
The Actions log tells you a test failed. It does not tell you whether that test has been failing all week, whether this branch made it worse, or what the browser was doing when it broke. Uploading the HTML report as an artifact gets you a zip to download and a local server to start. kinora takes the results straight from the job: every run is kept with its commit and branch, the pull request gets a comment listing what newly failed, and the full Playwright trace opens inline.
kinora.dev/project
Commit, branch, and run linked
The commit SHA, branch, base branch, and the Actions run URL are picked up from the job environment, so every run in kinora points back at the workflow that produced it.
A comment on the pull request
On a pull_request run, kinora posts pass/fail counts and the tests newly failing versus the base branch, then edits that same comment on every re-run. It uses the job's own GITHUB_TOKEN, so no credentials are stored.
Traces without the artifact dance
No upload-artifact, no download, no local show-trace. Click a red test and the real Playwright trace viewer opens in the dashboard.
FAQ
How do I publish a Playwright report from GitHub Actions?
Add @kinora/reporter to your playwright.config, store a kinora API token as a repository secret, and pass it to the test step as KINORA_TOKEN. The reporter uploads results when the run ends; nothing else in the workflow changes.
Can kinora comment on the pull request?
Yes. On pull_request runs it posts a summary with pass/fail counts and the tests newly failing versus the base branch, and updates that same comment on re-runs. The job needs pull-requests: write permission. Pull requests from forks are skipped, because their GITHUB_TOKEN is read-only.
Does it work with sharded or matrix jobs?
Yes. Merge shards with Playwright's merge-reports so the run uploads once as a single report. For matrix legs that share one pull request, give each leg its own PR comment label so they keep separate comments.
Awaiting first signal
Push your first run.
Add the reporter, point it at a kinora server, and watch the history build itself.