By default, matrix jobs use fail-fast behavior. What does setting 'strategy.fail-fast: false' change?
Select an answer to reveal the explanation.
Short Explanation and Infographic
fail-fast: false keeps sibling matrix jobs running when one combination fails, so you see the full cross-product results instead of cancelling the rest early.
Full explanation below image
Full Explanation
With the default fail-fast: true, when one job in a matrix fails, GitHub cancels the other in-progress matrix jobs in that strategy. Setting fail-fast: false disables that cancellation so every combination runs to completion. That is useful when you want full OS and version coverage feedback in a single run. It does not mark the workflow as successful if jobs failed — failed jobs still fail the matrix overall. It does not auto-retry failures; retries are a separate re-run action or custom logic. Failures remain failures, not warnings. Combine fail-fast: false with max-parallel to control load while still collecting complete results across the matrix.