aaryangorde/flake-finderv0.1.9Public
Flake finder
Which of your CI jobs fail at random? `gh run list` cannot tell you, and not for want of a flag: it prints one line per run carrying a run-level conclusion, so a red run on a 134-job matrix names none of the 134, and nothing in it groups a job across the runs it appeared in.
Read the full description
Flakiness is only visible on those two axes at once, per job and across history, which is why every single-run tool walks past it. This play samples recent completed runs on the default branch, where the code is presumably good, fans the job listings out in parallel, and groups every conclusion by job name. A job that both passed and failed there is flaky, an intermittent failure rather than a permanent one, reported with its rate and counts; a job that only ever failed is broken, a different problem, listed separately. Cancelled and skipped runs are counted and shown but never scored as failures, because a busy default branch cancels superseded runs constantly and counting those would manufacture flakes that do not exist. A single failur
Before you run it3 local tools
Everything here is checked on your machine when rote inspects the play. This page never learns what you have installed or which credentials you hold.
- ○ghlocal tool
Requires >=2.30.0. Run rote play inspect to check your host; unverified versions remain unknown.
- ○bashlocal tool
Must be on your PATH when used. minimum version undeclared.
- ○sleeplocal tool
Must be on your PATH when used. minimum version undeclared.
Inputs3, 1 required
rote asks for these before running and shows the defaults it will use.
- Repo
repoGitHub repository as owner/name
requiredstringexampledenoland/denocustom value allowed - Runs
runsHow many recent completed default-branch runs to sample
optionalnumberdefault12custom value allowed - Workflow
workflowRestrict to one workflow name; empty samples every workflow
optionalstringcustom value allowed
What it changes
No write operations are declared in this version's manifest.
Credentials remain in the recipient's local rote vault; this page and the publisher never receive them.
Runtime details
- rote CLIversion 0.62.0 or newer
- Servicesnone declared
- Digest
sha256:a92b3ccbb294954e7e5d7e7f7a2781ca771a31dba0be894f86744647fd0ab221 - Archive size7742 bytes
- Published2026-09-03T19:02:17.803152+00:00
- Published withrote 0.78.0
Credential values and current readiness remain local. Opening this page never prompts for a credential, opens an authorization browser, or calls a service this play uses.
A play is a published, versioned automation package that runs on your own machine through rote, a free command-line tool. Opening this page installs nothing and runs nothing.