Version Control
Post Playwright test results to GitHub pull requests as check runs
Tynkr posts test results directly to GitHub pull requests as check runs with pass/fail status. When all workflow steps pass, the check run turns green and unblocks the merge automatically. When a step fails, the check run links directly to the execution trace with the failure details — no CI log digging required.
What you can do
- Block pull request merges when critical Playwright tests fail
- Post a test summary comment on every PR with pass/fail breakdown
- Unblock merges automatically when all tests pass on the target branch
- Link flake-classified failures separately so they do not block valid PRs
Common questions
How does Tynkr post Playwright results to GitHub pull requests?
Tynkr connects to GitHub via the GitHub App. When a workflow completes, Tynkr posts a check run to the commit SHA with the overall pass/fail status. If the workflow fails, the check run includes a direct link to the execution trace in Tynkr so the developer can review the failure without leaving GitHub.
Can Tynkr block GitHub pull request merges on test failure?
Yes. When you configure the Tynkr GitHub App, you can set the Tynkr check run as a required status check for your branch protection rules. If the workflow fails, the check run fails and the merge is blocked until the failure is resolved or the workflow is re-run successfully.