This guide is the shortest path from "I found the project" to "I have a useful decision on a real CI failure."
CI Retry Gate is conservative by design. Start read-only, observe decisions, then enable write behavior only if the evidence is useful for your repository.
Use the public-run analyzer:
https://github.com/achirothmane/workflow-failure-lab/issues/new?template=public-run-analysis.yml
Provide:
- a public repository in
owner/repoform; - a failed GitHub Actions run ID.
The analyzer does not modify the target repository.
A result looks like:
Decision: BLOCK
Evidence: CONTRADICTED
Next action: STOP_RETRY_LOOP
Eligible failed jobs: 0
Blocked failed jobs: 1
The useful question is not "did the tool say ALLOW?" It is:
Did the result make the retry-versus-investigate decision clearer?
If not, stop here.
Create:
.github/workflows/ci-retry-gate.yml
with:
name: CI Retry Gate
on:
workflow_run:
workflows: ["CI"]
types: [completed]
permissions:
actions: read
checks: read
jobs:
retry-gate:
if: ${{ github.event.workflow_run.conclusion == 'failure' }}
runs-on: ubuntu-latest
steps:
- uses: achirothmane/workflow-failure-lab@v1
with:
github-token: ${{ github.token }}
auto-rerun: 'false'
selective-rerun: 'false'This evaluates failed runs but does not rerun them.
Create a temporary manual workflow:
name: CI Retry Gate Doctor
on:
workflow_dispatch:
permissions:
contents: read
actions: read
checks: read
jobs:
doctor:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- id: doctor
uses: achirothmane/workflow-failure-lab/doctor@v1
with:
github-token: ${{ github.token }}
source-workflow: 'CI'
rerun-mode: 'none'Doctor reports one of:
READYWARNBLOCKED
and gives concrete fixes.
- Analyze one historical failure.
- Install report-only mode.
- Run Setup Doctor.
- Observe decisions on real failures.
- Enable only the write behavior you actually need.
Use:
achirothmane/workflow-failure-lab@v1
for the stable v1 line.
For immutable builds, pin an exact release tag or commit SHA.
- README — product overview
- Product architecture — how the system is organized
- Technical reference — full inputs, outputs, and implementation details
- Examples — copy-ready workflows and fixtures