Pull and Merge Requests

The Pull Requests view lists the project’s GitHub pull requests or GitLab merge requests with their test results. Each row shows the request and a status breakdown of its tests, with segments linking into the detailed report. For GitHub projects, the same classification powers the Flakiness.io check posted on the pull request.

Regression

A regression is a failing test that the pull or merge request is responsible for — either an existing test that was passing on the target branch and now fails, or a brand-new test that fails on first run. See Concepts → Regressions for the mechanics.

How It Works

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

1. Collects test data from all test runs associated with the request.
2. Compares results against the target branch history to classify each failure. An existing test with a perfect recent history on the target branch that now fails is a regression. A test that has been flaky or failing on the target branch is not.
3. Flags brand-new tests that fail (tests the request adds that don’t pass) as regressions too.
4. Reports status back to GitHub via a Flakiness.io check when the project is connected to GitHub.

Reporting back to GitHub

For GitHub projects, Flakiness.io posts a Flakiness.io status check on the pull request, titled with the outcome breakdown. The check appears once the first test results arrive. It fails when the pull request has at least one regression or one failing test, and passes when it has neither. Flaky tests do not fail the check.

Flakiness.io also maintains a comment on the pull request listing the regressed, failed, and flaky tests with links into their reports. Both the check and the comment are configured per project. See GitHub Reporting.

Fix Regressions with AI Agents

If your project has the AI Agents skill installed, you can ask Claude Code, Codex, or Cursor to fix the regressions directly: “Fix the failing tests in PR #42 in myorg/myproject”. The agent will query Flakiness.io for the regressed tests, read their stack traces, and make the fix.

Pull Requests from Forks

Open-source projects that accept contributions from forks need a slightly different setup because GitHub doesn’t expose secrets or OIDC to fork-PR workflows. See GitHub Actions for Open Source Projects for the two-workflow pattern.