moar logic and responses

Author: mattdavis0351

config.yml

@@ -41,6 +41,8 @@ steps:
             data:
               title: Initial Workflow
           # if those gates === true Then do this stuff
+      - type: closeIssue
+        issue: Start Here!
       - type: respond
         with: 01_explain-workflow.md
         data:
@@ -101,49 +103,39 @@ steps:
           issueUrl: "%actions.devEnv.data.html_url%"
         pullRequest: Initial Workflow
       - type: mergePullRequest
-      # - type: respond
-      #   with: 03_on-to-actions.md
-      #   data:
-      #     issueUrl: "%actions.devEnv.data.html_url%"
-
-  # - title: Install an editor and Node.js along with required packages
-  #   description: Installing the necessary tools and begin writing an Action
-  #   event: pull_request.closed # Change this to when the pr is merged
-  #   actions:
-  #     - type: respond
-  #       with: install-tools.md
-  #       issue: Setting up your development environment
-  #     - type: respond
-  #       with: 04_configure-env.md
-  #       issue: Setting up your development environment
 
   - title: Creating the Action metadata
     description: Create an action.yml file and add necessary metatdata for our Action
-    event: pull_request
+    event: push
     # link: "{{ repoUrl }}/issue1/1"
     actions:
       - type: gate
-        gates:
-          # if the payload action is 'opened' OR 'edited'
-          - left: "%payload.action%"
-            operator: ===
-            right: opened
-          - left: "%payload.action%"
-            operator: ===
-            right: edited
-            # AND the pull request title equals 'Initial Workflow'
+        left: "%payload.ref%"
+        operator: ===
+        right: "refs/heads/hello-world"
       - type: gate
-        left: "%payload.pull_request.title%"
+        left: "%payload.created%"
         operator: ===
-        right: Hello Actions
-
-        # if those statments FAIL... do this
-        else:
-          - type: respond
-            with: e-rename-pr.md
-            data:
-              title: Initial Workflow
+        right: true
+      - type: createPullRequest
+        title: Hello Action
+        body: 04_explain-metadata.md
+        head: hello-world
+        action_id: helloPr
+      - type: respond
+        with: 04_hello-pr.md
+        issue: Setting up your development environment
+        data:
+          pullUrl: "%actions.helloPr.data.html_url%"
       - type: closeIssue
         issue: Setting up your development environment
       - type: respond
-        with: 04_explain-metadata.md
+        with: 04_create-metadata.md
+        issue: Hello Action
+
+  - title: Create the Action entrypoint
+    description: time to start adding code to main.js
+    event: pull_request.synchronize
+    actions:
+      - type: respond
+        with: 04_explain-runs.md

responses/04_configure-env.md

@@ -0,0 +1,41 @@
+## Enough talk, lets do this!
+
+Now that we know what Action metadata is, let's create the metadata for our current **hello-world** Action.
+
+I will be doing this from within [Visual Studio Code](https://code.visualstudio.com/) and that will be reflected in the images that I show you.  If you are using a different editor then your screen may look different.
+
+### :keyboard: Activity: Create the metadata file
+
+💡All of the following steps take place inside of the `.github/actions/hello-world` directory. 
+
+We will start with using the parameters that are **required** and later implement some optional parameters as our Action evolves.
+
+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.
+
+<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>
+
+```yaml
+name: "my hello action"
+
+description: "say hello with Actions"
+
+runs:
+  using: "node12"
+  main: "main.js"
+```
+</details>
+
+</details>
+
+5. Save the `action.yml` file
+6. commit the changes:
+   `git add .`
+   `git commit -m 'update action.yml'`
+7. push them to the `hello-world` branch:
+   `git push`
+   

responses/04_create-metadata.md

@@ -1 +1,22 @@
-### Explain action.yml
+## 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`
+- 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>
+
+---
+
+📖Read more about [Action metadata](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions)

responses/04_explain-metadata.md

@@ -0,0 +1 @@
+# explain runs

responses/04_explain-runs.md

@@ -0,0 +1,5 @@
+## Great job 👍
+
+I have created a [new pull request]({{pullUrl}}) where we will continue this lesson.  Click the link to meet me over there.
+
+In the meantime I have closed this issue since we wont be needing it anymore 😄

responses/04_hello-pr.md

@@ -0,0 +1 @@
+## some main js

responses/04_main-js.md

@@ -12,9 +12,9 @@ If you do not have a preferred environment then I suggest following along with m
 
 Most of your work going forward will take place away from your Learning Lab repository, so before continuing with the course ensure you have the following installed on your **local machine**.  
 
-1. [Node.js](https://nodejs.org)
-2. [Visual Studio Code](https://code.visualstudio.com/) or your editor of choice
-3. [Git](https://git-scm.com/)
+1. [ ] [Node.js](https://nodejs.org)
+2. [ ] [Visual Studio Code](https://code.visualstudio.com/) or your editor of choice
+3. [ ] [Git](https://git-scm.com/)
 
 
 ### :keyboard: Activity: Configure your environment
@@ -23,7 +23,7 @@ Now that you have all the necessary tools installed locally, follow these steps
 
 1. Open the **Terminal** (Mac and Linux) or **Command Prompt** (Windows) on your local machine
 2. Clone your Learning Lab repo to your local machine:
-   `git clone https://{{repoUrl}}.git`
+   `git clone {{repoUrl}}.git`
    <details><summary>View GIF</summary><img src="https://media.giphy.com/media/YnvmISGo2MbXpn2bc5/giphy.gif" alt="git clone example" /></details>
     <!-- ![alt text](https://media.giphy.com/media/YnvmISGo2MbXpn2bc5/giphy.gif) -->
 
@@ -37,14 +37,28 @@ Now that you have all the necessary tools installed locally, follow these steps
 
 5. Create a new folder for our Actions files:
    `mkdir -p .github/actions/hello-world`
+    <details><summary>View GIF</summary><img src="https://media.giphy.com/media/Wn03sc0QsywHHD1LeN/giphy.gif" alt="create folder for action example" /></details>
 6. Navigate to the `hello-world` folder you just created:
    `cd .github/actions/hello-world`
-7. Initialize the a new project with `npm init -y`
-8. Install the **core** and **github** dependencies from the [GitHub ToolKit](https://github.com/actions/toolkit) by typing `npm install --save @actions/core @actions/github`
-9.  Commit those newly added files, including `node_modules`, we will remove the need to upload `node_modules` in a later step
+    <details><summary>View GIF</summary><img src="https://media.giphy.com/media/ckCMgczjpbjNwkfJq4/giphy.gif" alt="navigate to folder for action example" /></details>
+   
+7. Initialize a new project:
+   `npm init -y`
+    <details><summary>View GIF</summary><img src="https://media.giphy.com/media/mEW0fJYx4oUjdgYHDV/giphy.gif" alt="navigate to folder for action example" /></details>
+
+8. Install the **core** and **github** dependencies from the [GitHub ToolKit](https://github.com/actions/toolkit):
+   `npm install --save @actions/core @actions/github`
+   <details><summary>View GIF</summary><img src="https://media.giphy.com/media/H3kGNqDI24lNOEKk5k/giphy.gif" alt="navigate to folder for action example" /></details>
+9.  Commit those newly added files,we will remove the need to upload **node_modules** in a later step:
+    `git add .`
+    `git commit -m 'initial hello-world'`
 10. Push you changes to your repository:
     `git push -u origin hello-world`
-11. Create a new pull request from the `hello-world` branch to `master` with the title of `Hello Actions`
-    - Take notice that the pull request name `Hello Actions` is case-sensitive
 
-I will close this issue and continue responding to you in the `hello-actions` pull request once you have created it.
+
+---
+
+I will respond once you have finished.
+
+
+