PR reporting

When you bind a GitHub repo to a project, Matcha can run against your changes and report back on the pull request. It posts a comment that summarizes the runs and links each one to a full report. To bind a repo, see the GitHub integration.

The PR comment

Matcha maintains one comment on the pull request and updates it in place as runs progress. The comment opens with an overview row:

• Result: the combined outcome, showing failed, warning, running, or passed counts.
• Dashboard: a link to open the target.
• Duration: how long the runs took.
• Commit: the head commit the runs used.
• Updated: when Matcha last updated the comment, in UTC.

Below the overview, the comment links each run to its report. The report page is gated by GitHub sign-in: a signed-in user can open it only with at least read permission on the tested repo. Matcha answers that check with the GitHub App's own installation token, so a viewer's token is never stored. If you need a report that anyone can open without GitHub access, mint a share link instead.

Deployment-driven runs

A run can start from a GitHub deployment. When a deployment for the bound repo succeeds, Matcha runs the tests whose trigger is that deployment, against the deployment's URL. This is how a preview or staging deploy gets QA without anyone starting a run by hand.

If the deployment is gated, set up site protection so Matcha can reach the app behind the gate.

PR build runs

You configure PR testing in Coldtea settings, under QA, then GitHub PR testing. You choose the group or groups whose tests run on a qualifying pull request, and the target branch. On a qualifying PR, Matcha fans out runs for each configured group, each under its own group identity, and reports them in the PR comment.

Fresh mobile build QA extends this to Android and iOS: Matcha runs saved mobile scenarios against the app build from the PR's own GitHub Actions run. See mobile CI artifacts for the artifact setup.

Related

• GitHub integration: bind the repo and install the GitHub App.
• Tests and groups: the groups a PR run fans out to.
• Share a run: a public report for people without repo access.