What is the benefit of using 'Re-run failed jobs' instead of 'Re-run all jobs' after a workflow failure?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Re-run failed jobs is the smart retry — it skips jobs that already passed, saving minutes and giving you faster feedback on the actual failures.
Full explanation below image
Full Explanation
'Re-run failed jobs' re-runs only the jobs that failed or were cancelled, plus any jobs that depend on them. Jobs that already passed are not re-run, saving billing minutes and reducing turnaround time. 'Re-run all jobs' restarts the entire workflow from scratch, including jobs that passed. 'Re-run failed jobs' uses the same runner queue as a normal run — it doesn't select different runners for debugging. Job dependencies (needs:) are still respected in re-runs. This feature is accessible in the GitHub UI and via 'gh run rerun --failed' in the CLI.