-
Notifications
You must be signed in to change notification settings - Fork 61.7k
jobs.<job_id>.strategy.fail-fast
docs don't specify wheather "all jobs" refers to the workflow, or the job matrix
#16401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
jobs.<job_id>.strategy.fail-fast
docs don't specify wher "all jobs" refers to the workflow, or the job matrixjobs.<job_id>.strategy.fail-fast
docs don't specify wheather "all jobs" refers to the workflow, or the job matrix
@michaelosthege |
The linked PR is not a PR to the docs (I still don't know the answer to my question) but the issue in our project that's tracking our effort to fast-fail our test jobs when the linting job fails. |
Ops! I meant to say thank you for opening this issue 💛 I apologize for the confusion 💖 |
It cancels just the jobs within the same matrix. I agree that the current wording does not make this super clear. We could update to be something like the following:
You (or anyone else!) can feel free to open a PR to make the ☝️ change. |
Code of Conduct
What article on docs.github.com is affected?
The
jobs.<job_id>.strategy.fail-fast
section:https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast
What part(s) of the article would you like to see updated?
I had (and still have) the following question, which is not answered by the corresponding docs section:
I think there are scenarios where either behavior is desired.
Additional information
I'm considering to use the
fail-fast
seting to cancel the entire workflow if thepre-commit
job fails, but while keeping their execution parallelized.The text was updated successfully, but these errors were encountered: