diff --git a/responses/03.0_actionyml-success.md b/responses/03.0_actionyml-success.md index 4c73d5e..273e366 100644 --- a/responses/03.0_actionyml-success.md +++ b/responses/03.0_actionyml-success.md @@ -8,7 +8,7 @@ Workflows can execute based on your chosen event. For this lab, we'll be using t We'll break down each line of the workflow in the next step. -## Step 3: Start your workflow file +## Step 4: Start your workflow file First, we'll add the structure of the workflow. diff --git a/responses/04.0_workflow-block-success.md b/responses/04.0_workflow-block-success.md index b2d4fc0..a324417 100644 --- a/responses/04.0_workflow-block-success.md +++ b/responses/04.0_workflow-block-success.md @@ -13,7 +13,7 @@ Workflows piece together jobs, and jobs piece together steps. We'll now create a We'll add the block now, and break it down in the next step. -## Step 4: Run an action from your workflow file +## Step 5: Run an action from your workflow file Let's add the expected action to the workflow. diff --git a/responses/05.0_trigger.md b/responses/05.0_trigger.md index 803d0a3..98cf2e1 100644 --- a/responses/05.0_trigger.md +++ b/responses/05.0_trigger.md @@ -20,7 +20,7 @@ The status of your action is shown here in the pull request (look for **All chec ![View an action's log](https://user-images.githubusercontent.com/16547949/62388049-4e64e600-b52a-11e9-8bf5-db0c5452360f.png) -## Step 5: Trigger the workflow +## Step 6: Trigger the workflow ### :keyboard: Activity: See your action trigger the workflow diff --git a/responses/06.0_workflow-success.md b/responses/06.0_workflow-success.md index 94caf65..ea50eaf 100644 --- a/responses/06.0_workflow-success.md +++ b/responses/06.0_workflow-success.md @@ -4,7 +4,7 @@ You should see the string "Hello world, I'm Mona!" printed at the bottom to `std ![Actions successful log file](https://user-images.githubusercontent.com/16547949/62388562-9fc1a500-b52b-11e9-8d7e-4f4d32450fd5.png) -## Step 6: Incorporate the workflow +## Step 7: Incorporate the workflow As a final step, merge this pull request so the action will be a part of the `master` branch.