removing redundancy in responses

Author: mattdavis0351

04_hello-result.md

@@ -122,6 +122,8 @@ steps:
         body: 04_explain-metadata.md
         head: hello-world
         action_id: helloPr
+        data:
+          actionsUrl: "%payload.repository.html_url%/actions"
       - type: respond
         with: 04_hello-pr.md
         issue: Setting up your development environment
@@ -139,19 +141,17 @@ steps:
     actions:
       - type: respond
         with: 04_explain-runs.md
+        data:
+          actionsUrl: "%payload.repository.html_url%/actions"
       - type: respond
         with: 04_main-js.md
         data:
           actionsUrl: "%payload.repository.html_url%/actions"
 
   - title: Adding input parameters
     description: extend your action to accept input parameters
-    event: check_suite.completed
+    event: pull_request.synchronize
     actions:
-      - type: gate
-        left: "%payload.check_suite.app.name%"
-        operator: ===
-        right: "GitHub Actions"
       - type: respond
         with: 04_hello-result.md
       - type: respond

config.yml

@@ -15,9 +15,7 @@ We will start with using the parameters that are **required** and later implemen
 3. Next, add a `description` parameter and give it a value of `"say hello with Actions"`
 4. Lastly, define the `run` parameter to use `"node12"` to execute the `"main.js"`
 
-    <details><summary>View the complete file</summary><img src="https://i.imgur.com/xCuBdI4.png" alt="screenshot of action.yml file" />
-
-    <details><summary>Raw code to copy</summary>
+    <details><summary>View the complete file</summary>
 
     ```yaml
     name: "my hello action"
@@ -30,7 +28,7 @@ We will start with using the parameters that are **required** and later implemen
     ```
     </details>
 
-    </details>
+
 
 5. Save the `action.yml` file
 6. commit the changes:

responses/04_create-metadata.md

@@ -1,5 +1,19 @@
 ## Action metadata
 
+#### The failing workflow
+Before we jump into the details of Action metadata, it might be helpful to examine our workflow to understand the order that things happen.  I have attached a screenshot below of the most recent workflow run, you can also follow along by clicking on the [Actions tab]({{actionsUrl}}) for your repository.
+
+![](https://i.imgur.com/FPOjK3R.png)
+
+Notice that our third workflow step, the one that is looking for our Action is failing.  We expect this, but the magic ✨is in the error message!  
+
+That step is looking for a specific file, and in our case it's looking for the `action.yml` file.  It's not looking for a JavaScript file or a `config.yml` file.
+
+Because that file is non-existent in the `hello-world` directory we see this error.  So let's start by talking about, and creating, that `action.yml` file.
+
+#### The need to know of Action metadata
+
+
 Every GitHub Action that we write needs to be accompanied by a metadata file.  This file has a few rules to it, lets outline those now:
 
 - Filename **must** be `action.yml`

responses/04_explain-metadata.md

@@ -21,6 +21,16 @@ runs:
   main: 'bread.js'
 ```
 
+#### From our workflows perspective
+
+This execution is visible from within your workflow.  To save time I have included a screenshot of what your workflow currently looks like.  As always, you can follow along in the [Actions tab]({{actionUrl}}).
+
+![A look into the failed run](https://i.imgur.com/nJtqEct.png)
+
+Look 👀, now we have a new error!  We are totally making progress here!  What we can reason from this output is that our `action.yml` file was found and read.  Since we defined the `main:` parameter to point to a file named `main.js` the workflow looked for that file in the root of the `hello-world` directory, but since it couldn't find it the workflow fails.
+
+Let's fix this next!
+
 ---
 
 Keep this in mind because later we will be referencing a file that is not in the same directory of the `action.yml`

responses/04_explain-runs.md

@@ -0,0 +1,3 @@
+result of workflow run
+
+![](https://i.imgur.com/NDQjAx6.png)

responses/04_hello-result.md

@@ -16,16 +16,14 @@ The first iteration of our Action will follow the traditional path of logging "H
 
 1. Create a file named `main.js`
 2. Log "Hello World" to the console
-    <details><summary>View the complete file</summary><img src="https://i.imgur.com/ABXoNtE.png" alt="screenshot of main.js file" />
-
-    <details><summary>Raw code to copy</summary>
+    <details><summary>View the complete file</summary>
 
     ```javascript
     console.log("Hello World")
     ```
     </details>
 
-    </details>
+
 3. Save the `main.js` file
 4. commit the changes:
    `git add .`