Pull Requests

Flakiness.io integrates with GitHub pull requests to detect test regressions introduced by code changes before they get merged.

Pull requests from forks

Open-source projects that accept contributions from forks need a slightly different setup. See the GitHub Actions integration guide for details.

How It Works

When tests run on a pull request, Flakiness.io:

1. Collects test data from all test runs associated with the PR
2. Compares results against the target branch history — regressions are detected by comparing PR test results against the historical test data of the branch you’re merging into (e.g. main), not just the latest commit
3. Reports status back to GitHub via a Flakiness.io check on the pull request

This means if a test has been consistently passing on the target branch and starts failing in your PR, Flakiness.io flags it as a regression — giving you confidence that the failure is caused by your changes, not by pre-existing flakiness.

GitHub Check

Flakiness.io posts a check on the pull request that summarizes test results: regressions, new failures, and overall test health. The check links directly to the Flakiness.io dashboard for the PR, where you can inspect individual test results in detail.