From c2c5e3e08b7ac5e8e1d25d5c9b484a76ad3fafe7 Mon Sep 17 00:00:00 2001 From: Sam <90829439+MizouziE@users.noreply.github.com> Date: Sun, 18 Aug 2024 12:27:12 +0300 Subject: [PATCH] Update section-using-jobs-in-a-workflow.md Explicitly state that at least one job is required to run and that without, a workflow will fail --- data/reusables/actions/jobs/section-using-jobs-in-a-workflow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/reusables/actions/jobs/section-using-jobs-in-a-workflow.md b/data/reusables/actions/jobs/section-using-jobs-in-a-workflow.md index 048ad31d2151..a0403ae43948 100644 --- a/data/reusables/actions/jobs/section-using-jobs-in-a-workflow.md +++ b/data/reusables/actions/jobs/section-using-jobs-in-a-workflow.md @@ -1,4 +1,4 @@ -A workflow run is made up of one or more `jobs`, which run in parallel by default. To run jobs sequentially, you can define dependencies on other jobs using the `jobs..needs` keyword. +A workflow run is made up of at least one or more `jobs`, which run in parallel by default. Without any jobs to run, a workflow will fail. To run jobs sequentially, you can define dependencies on other jobs using the `jobs..needs` keyword. Each job runs in a runner environment specified by `runs-on`.