Skip to main content
The primary surface for QLane’s PR-bound results is GitHub itself — a check run on every PR, plus a structured review when something broke.

​
The check run

Every PR with QLane enabled gets a single check run named QLane. It moves through three states: You can require the QLane check in your branch protection rules to block merges on regressions.

​
Silent on pass

When QLane finds nothing, you hear nothing — no PR comment, no review, no notification. The check just turns green. This is deliberate: every successful run that posts a comment is noise, and noise teaches your team to ignore the tool.

​
Reviews on failure

When QLane finds bugs, it posts a single GitHub review with:
  • A summary at the top: total passed, total failed, bug count, run duration, link to the dashboard.
  • One review comment per bug — anchored to the line of code most likely to be the culprit when QLane can pinpoint one, or to the PR description otherwise.
  • For each bug: severity, a one-line title, the exact reproduction steps, and a screenshot.
You can reply to a bug comment with @qlane fix to load the bug straight into your editor through the Claude Code integration.

​
Re-running

If the failure looks like a flake — or you’ve pushed a fix — click Re-run on the GitHub check. QLane spins up a new session against the latest PR head SHA and reposts the review.

​
Cancelling

Closing the PR cancels any in-flight session for it. You can also cancel from the session page in the dashboard.

​
Where the screenshots live

Screenshots, DOM snapshots, and the full agent trace are stored on the session in the QLane dashboard, linked from each bug comment. We don’t paste images into the GitHub comments themselves — review threads stay scannable, and the heavy assets stay one click away.