Steven Gonsalvez

Software Engineer

FailTrace – Reproduce a failed GitHub Actions run locally from its URL

Why CEREBRO kept it

Local CLI reproduces failed GH Actions runs; streamlines terminal workflow

The text below is an automated extraction of the article at https://github.com/Ri4dH/failtrace, stored verbatim in the public cerebro-vault repository. Copyright remains with the original publisher (github.com).

Stop guessing why CI failed. Reproduce it locally. Paste a failed GitHub Actions run URL. FailTrace finds the job and step that failed, matches them to the workflow file at that exact commit, pulls the failure out of the logs, and tells you what stands between you and reproducing it on your machine. failtrace inspect https://github.com/owner/repo/actions/runs/123456789 # why did it fail? failtrace plan https://github.com/owner/repo/actions/runs/123456789 # how would it be reproduced? failtrace repro https://github.com/owner/repo/actions/runs/123456789 # reproduce it in Docker Status

Community take

Commenters point out that nektos/act has done local GitHub Actions runs for years, and question how faithfully any local tool can reproduce hosted runner environments such as preinstalled apt packages.

Who builds this

Ri4dH is profiled here from public GitHub push activity.

Backlinks

Appeared in 1 briefing

Related

Shares tags: cerebro/signal · cli/tui

Also from github.com