adding final responses

Author: mattdavis0351

config.yml

@@ -300,7 +300,7 @@ steps:
         with: 07_use-fs.md
         data:
           columnID: "%actions.listColumns.data.0.id%"
-          quicklink: "%payload.repository.html_url%/edit/%payload.head.ref%/.github/workflows/my-workflow.yml"
+          quicklink: "%payload.repository.html_url%/edit/%payload.repository.head.ref%/.github/workflows/my-workflow.yml"
 
   - title: Merge the final workflow
     description: Merge the final workflow into the repository
@@ -311,8 +311,8 @@ steps:
       - type: respond
         with: 08_merge-workflow.md
 
-  - title: Course recap
-    description: Final remarks on course content
+  - title: See workflow results
+    description: See the results of the final workflow run
     event: pull_request.closed
     link: "{{repoUrl}}/issue/7"
     actions:
@@ -324,13 +324,35 @@ steps:
         body: |
           ## Great Job so far!  
 
-          Like before, now we have to wait for the
-          workflow to run so that we can see the results.  I'll respond here once it has completed!
+          Like before, now we have to wait for the workflow to run so that we can see the results.  
+
+          ---
+
+          I'll respond here once it has completed!
         labels: ["bug"]
+
+  - title: Open an issue
+    description: Open another issue that does not contain the bug tag
+    event: check_suite.completed
+    link: "{{repoUrl}}/issue/7"
+    actions:
       - type: respond
         with: 09_workflow-completed.md
         issue: 7
-      # - type: createIssue
-      #   title: It's alive!
-      #   body: 09_workflow-triggered
-      #   action_id: triggerIssue
+      - type: respond
+        with: 09_issue-activity.md
+        issue: 7
+        data:
+          quicklink: "%payload.repository.htm_url%/issues/new"
+
+  - title: Course recap
+    description: Final notes on course
+    event: check_suite.completed
+    link: "{{repoUrl}}/issue/8"
+    actions:
+      - type: respond
+        with: 10_workflow-completed.md
+        issue: 8
+      - type: respond
+        with: 10_course-recap.md
+        issue: 8

responses/09_issue-activity.md

@@ -0,0 +1,11 @@
+### :keyboard: Activity: Create a new issue in this repository
+
+1. [Click here]({{quicklink}}) to quickly open a new issue
+1. Give the issue a name of your choosing
+1. Supply the issue with a body
+1. Be sure NOT to include the bug label on this issue
+1. Click the `Submit new issue` button
+
+---
+
+I'll respond in your new issue once you've opened it

responses/09_workflow-completed.md

@@ -1 +1,9 @@
-# super awesome workflow has been triggered
+## Another workflow success
+
+Great job yet again!
+
+As you can see, there is now a more comprehensive response to a new issue being opened, and it's based on a template in this repository so it's easy to change in the future. Along with that change, this issue has now been added to the project board so that we can be reminded to triage it for work!
+
+**What about all the extra logic?**
+
+You're right! We added some expression logic to the workflow that will only add an issue to the project board, if it contains the `bug` label at the time of creation. Let's see if our logic works as intended!

responses/10_course-recap.md

@@ -0,0 +1,19 @@
+## What you learned
+
+As we wrap this course up it's important that we revisit the learning points you encountered along the way.
+
+**Things you learned in this course:**
+
+- What GitHub Script is
+- How GitHub Script maps to octokit/rest.js
+- How to use the GitHub Script action in your workflow
+  - By commenting when an issue is opened
+  - By adding an issue to a project board when it is opened
+- How to read a file from the repository for use with GitHub Script
+- How to apply expressions to a workflow file
+
+That should give you quite the start with incorporating the GitHub Script action into your workflows!
+
+---
+
+Congratulations on finishing this course. You will receive no further responses from me, however further action taken in this repo could trigger workflow runs, because of this we recommend commenting out the workflow file if you plan to keep this repository for notes!

responses/10_workflow-completed.md

@@ -0,0 +1,5 @@
+## Whoo hoo 🎉
+
+Super awesome job @{{user.login}}! As you can see, your workflow still commented on this issue, but it did not add it to the project board!
+
+Don't hesitate to experiment with changes to the current workflow to see if what kind of logic you can implement to change the response to an issue based on the conditions that surround your own software development lifecycle!