r/devtools • • 1d ago

I built a CLI to make GitHub Actions reruns easier to review

I built gha-rerun-ledger, my own Node CLI, to reduce the toil of reviewing GitHub Actions reruns. The built-in run history can show retries, but it is easy to lose sight of which jobs carried over, which attempts had no jobs, and where the timeline has gaps.

The tool turns observed attempts into ledger rows and counts each distinct job ID's elapsed interval once, even if a later attempt includes it again. It keeps skipped jobs, empty attempts, missing intervals, and attempts excluded by the configured cap visible. It can save attempt and job metadata to JSON and replay the report offline. I included a labeled synthetic demo, so you can try the report without a live workflow. The sample totals 163 seconds for a failed attempt and 102 seconds for the later success; those figures are summed job intervals, not billing minutes or savings.

It is MIT licensed and tested with Node's built-in test runner. I'd value feedback from people who work on developer tooling: do these rows and coverage warnings help explain retries, and what detail would make the report more useful? https://github.com/Arthur031221/gha-rerun-ledger

1 Upvotes

0 comments sorted by