ci-triage

ci-triage

CI is red. Which failure matters, and is it a real regression or just flaky?

ci-triage answers that in one page: it fetches a repo's recent failed GitHub Actions runs, reads the failed job logs, groups failures by root cause, and tells you which ones are real regressions and which are flaky — so you fix the one thing that matters instead of reading thousands of log lines by hand.

Before / after

Before: CI is red on 3 runs. You open each run, find the failed job, scroll through the log, and try to remember whether you saw this error yesterday.

After:

$ ci-triage acme/widgets

ci-triage — acme/widgets
Window: 2 recent runs listed, 2 failed examined
Root causes: 1 (1 real, 0 flaky)

#1  test · 2 runs · real regression
    FAIL src/components/Button.test.tsx
    3 test-runner failure signals in the error lines. fails on every recent run — looks like a real regression, not flakiness.
    first seen 2026-11-12 10:00 · last seen 2026-11-12 14:03
    runs: #2 (test), #1 (test)
    evidence:
      FAIL src/components/Button.test.tsx
      ● Button › renders the disabled state
      expect(received).toBe(expected) // Object.is equality

---

View the full README on GitHub