adding more logic and responses

Author: mattdavis0351

config.yml

@@ -139,3 +139,18 @@ steps:
     actions:
       - type: respond
         with: 04_explain-runs.md
+      - 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
+    actions:
+      - type: gate
+        left: "%payload.check_suite.app.name%"
+        operator: ===
+        right: "GitHub Actions"
+      - type: respond
+        with: 04_add-input-params.md

responses/03_reference-actions.md

@@ -25,7 +25,7 @@ If you'd like to see more examples of workflows and Actions then check out these
 
 1. [Edit]({{workflowFile}}) the `my-workflow.yml`.
 1. Add a new `step:` and `name:` it `hello-action`
-1. Set the value of `uses:` to `./.github/actions/hello-world`
+1. Set the value of `uses:` to `.github/actions/hello-world`
 1. Commit these file changes to this branch
 
 ---
@@ -46,6 +46,6 @@ jobs:
     - uses: actions/checkout@v1
 
     - name: hello-action
-      uses: ./.github/actions/hello-world
+      uses: .github/actions/hello-world
 ```
 </details>

responses/04_add-input-params.md

@@ -0,0 +1 @@
+# add input parameters

responses/04_create-metadata.md

@@ -13,24 +13,24 @@ We will start with using the parameters that are **required** and later implemen
 1. Create a file named `action.yml`
 2. Use the `name` parameter to name your Action `"my hello action"`
 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"` file that doesn't exist yet.
+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>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>Raw code to copy</summary>
 
-```yaml
-name: "my hello action"
+    ```yaml
+    name: "my hello action"
 
-description: "say hello with Actions"
+    description: "say hello with Actions"
 
-runs:
-  using: "node12"
-  main: "main.js"
-```
-</details>
+    runs:
+      using: "node12"
+      main: "main.js"
+    ```
+    </details>
 
-</details>
+    </details>
 
 5. Save the `action.yml` file
 6. commit the changes:

responses/04_explain-metadata.md

@@ -3,19 +3,21 @@
 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`
-- Placed in the root directory of your Action
 - Required for both Docker container and JavaScript Actions
 - Written in YAML syntax
 
 This file defines the following information about your Action:
 
-<details><summary>Name</summary>This parameter is <b>required</b>. The name of your action. Helps visually identify the Actions in a job.</details>
-<details><summary>Author</summary>This parameter is <b>optional</b>. The name of who wrote the Action.</details>
-<details><summary>Description</summary>This parameter is <b>required</b>. A summary of what your Action does.</details>
-<details><summary>Inputs</summary>This parameter is <b>optional</b>. Input parameters allow you to specify data that the action expects to use during runtime. These parameters become environment variables in the runner.</details>
-<details><summary>Outputs</summary>This parameter is <b>optional</b>.  Specifies the data that subsequent actions can use later in the workflow after the action that defines these outputs has run.</details>
-<details><summary>Runs</summary>This parameter is <b>required</b>.  The command to run when the Action executes.</details>
-<details><summary>Branding</summary>This parameter is <b>optional</b>.  You can use a color and Feather icon to create a badge to personalize and distinguish your action in GitHub Marketplace.</details>
+
+
+| Parameter   | Description                                                                                                                                            |      Required      |
+| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | :----------------: |
+| Name        | The name of your Action. Helps visually identify the Actions in a job.                                                                                 | :white_check_mark: |
+| Description | A summary of what your Action does.                                                                                                                    | :white_check_mark: |
+| Inputs      | Input parameters allow you to specify data that the action expects to use during runtime. These parameters become environment variables in the runner. |         ❌          |
+| Outputs     | Specifies the data that subsequent actions can use later in the workflow after the action that defines these outputs has run.                          |         ❌          |
+| Runs        | The command to run when the Action executes.                                                                                                           | :white_check_mark: |
+| Branding    | You can use a color and Feather icon to create a badge to personalize and distinguish your action in GitHub Marketplace.                               |         ❌          |
 
 ---
 

responses/04_explain-runs.md

@@ -1 +1,26 @@
-# explain runs
+## Runs
+
+As you have learned `runs:` defines the command necessary to execute your Action.
+
+In our current case `runs:` takes 2 arguments
+
+- `using:`
+- `main:`
+
+These are specific to JavaScript Actions.  It is our way of telling the runner to run the `main.js` file using `node12`
+
+This is no different than running a local JavaScript file using Node like you see below:
+![node example](https://media.giphy.com/media/W1kCFFsaoYlsmpVtxv/giphy.gif)
+
+Which means that the value of `main:` would be different if your file was not named `main.js`.  
+![different filename example](https://media.giphy.com/media/H7CCHqH06pVbQeWmlb/giphy.gif)
+In this scenario our metadata block would look like this:
+```yaml
+runs:
+  using: 'node12'
+  main: 'bread.js'
+```
+
+---
+
+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_main-js.md

@@ -1 +1,37 @@
-## some main js
+## Time to code 💻
+
+You may have noticed that your workflow has been running every time a change has been made.  This is expected since it's trigger is a `push` event.
+
+Hopefully you have also noticed that it fails when it reaches the `hello-action` step.
+
+As we can see from the screenshot, as well as the [Actions]({{actionsUrl}}) tab, the failure occurs because the runner cannot find the Action.  
+
+Lets fix that by creating the Action it is looking for!
+
+### :keyboard: Activity: Hello World
+
+💡All of the following steps take place inside of the `.github/actions/hello-world` directory. 
+
+The first iteration of our Action will follow the traditional path of logging "Hello World" 👋to the console.  We will expand on this as we move forward, for now it's a good test to make sure all of our files are set up correctly 😄
+
+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>
+
+    ```javascript
+    console.log("Hello World")
+    ```
+    </details>
+
+    </details>
+3. Save the `main.js` file
+4. commit the changes:
+   `git add .`
+   `git commit -m 'create main.js'`
+5. push them to the `hello-world` branch:
+   `git push`
+
+---
+I'll respond here once the workflow has completed running.  Remember, you need to **push** your changes to trigger it!