more prep for release

Author: mattdavis0351

config.yml

@@ -2,6 +2,11 @@ title: "GitHub Actions: Using GitHub Script"
 description: >-
   This course covers how to use GitHub Script to quickly use octokit/rest in a
   GitHub Actions workflow.
+tags:
+  - GitHub Actions
+  - Octokit
+  - Workflow
+  - Automation
 template:
   repo: write-github-script-template
   name: write-github-script
@@ -54,36 +59,24 @@ steps:
       # get tree
       - type: getTree
         action_id: isInTree
-        store:
-          firstWorkflowTree: "%result.data.tree%"
         recursive: true
         sha: "%payload.pull_request.head.sha%"
-      - type: respond
-        with: e-result.md
-        data:
-          resultData: "%registration.store.firstWorkflowTree%"
-          actionIdData: "%actions.isInTree.data.tree%"
       # check for a file in a tree
       - type: gate
-        # left: "%actions.isInTree.data.tree%"
-        left: "%registration.store.firstWorkflowTree%"
+        left: "%actions.isInTree.data.tree%"
         operator: includes
         right: "path:.github/workflows/my-workflow.yml"
         else:
           # if file isn't where expected find true location
           - type: findInTree
             path: my-workflow.yml
-            # tree: "%actions.isInTree.data.tree%"
-            tree: "%registration.store.firstWorkflowTree%"
-            # action_id: fileLocation
-            store:
-              firstFileLocation: "%result.data.path%"
+            tree: "%actions.isInTree.data.tree%"
+            action_id: fileLocation
           # help user with proper file location
           - type: respond
             with: e-wrong-file-location.md
             data:
-              # haveFile: "%actions.fileLocation.path%"
-              haveFile: "%registration.store.firstFileLocation%"
+              haveFile: "%actions.fileLocation.path%"
               needFile: ".github/workflows/my-workflow.yml"
               editLink: "%payload.repository.html_url%/edit/%payload.pull_request.head.ref%/%actions.fileLocation.path%"
               fileName: my-workflow.yml
@@ -103,7 +96,7 @@ steps:
           firstPullUrl: "%result.data.html_url%"
           firstPullNumber: "%result.data.number%"
         data:
-          actionsUrl: "%payload.repository.html_url%/actions"
+          actionsUrl: "%payload.repository.html_url%/actions%"
 
   - title: Merge the new workflow into the master branch
     description: Make the workflow available for use on the repository
@@ -113,7 +106,6 @@ steps:
       - type: createIssue
         title: Create an issue comment with GitHub Script
         body: 02_workflow-triggered.md
-        # action_id: triggerIssue
         store:
           secondIssueNumber: "%result.data.number%"
           secondIssueUrl: "%result.data.html_url%"

responses/00_welcome-activity.md

@@ -62,4 +62,4 @@ _It is important to place meaningful content into the body of the pull requests
 
 ---
 
-I'll respond in the new pull request when I detect it has been created.
+I am waiting for you to create a new pull request before moving on.

responses/01_merge-workflow.md

@@ -8,12 +8,12 @@ Let's go ahead and do this now.
 
 ### :keyboard: Activity: Merge the workflow
 
-When you are ready, merge this pull request.
+1.  Merge this pull request.
 
 ---
 
-Once you have merged this pull request I will open a new issue so we can see this workflow in action!
+I am waiting for you to merge this pull request before moving on.
 
-Oh, I'll also be responding to you from that issue!
+Once you have merged this pull request I will open a new issue so we can see this workflow in action!
 
 <details><summary>Trouble merging?</summary>Try refreshing the page!</details>

responses/03_add-to-projects.md

@@ -50,4 +50,6 @@ We've gone ahead and done this on our end of things so that we could give you th
 
 ---
 
+I am waiting for you to create a new pull request before moving on.
+
 I'll respond in the new pull request when I detect it has been created.

responses/04_merge-workflow.md

@@ -14,6 +14,8 @@ When you are ready, merge this pull request.
 
 ---
 
+I am waiting for you to merge this pull request before moving on.
+
 Once you have merged this pull request I will open a new issue so we can see this workflow in action!
 
 <details><summary>Trouble merging?</summary>Try refreshing the page!</details>

responses/06_steps-activity.md

@@ -52,4 +52,6 @@ We will make the following changes to the current workflow file:
 
 ---
 
+I am waiting for you to create a new pull request before moving on.
+
 I'll respond in the pull request you create

responses/07_use-fs.md

@@ -55,4 +55,6 @@ We will make the following changes to the current workflow file:
 
 ---
 
+I am waiting for you to commit the desired changes to this branch before moving on.
+
 I'll respond once you've committed the changes to this branch

responses/08_merge-workflow.md

@@ -8,6 +8,8 @@ When you are ready, merge this pull request.
 
 ---
 
+I am waiting for you to merge this pull request before moving on.
+
 Once you have merged this pull request I will open a new issue so we can see this workflow in action!
 
 <details><summary>Trouble merging?</summary>Try refreshing the page!</details>

responses/09_issue-activity.md

@@ -8,4 +8,6 @@
 
 ---
 
+I am waiting for you to open a new issue before moving on.
+
 I'll respond in your new issue once you've opened it

server-installation-notes.md

@@ -0,0 +1,24 @@
+## GitHub Enterprise Server (GHES) installation notes
+
+<!-- start compatibility header, pick one of the options below, add or remove detail as necessary -->
+
+| 🚫  | This course needs features not yet supported by GHES. |
+| --- | ----------------------------------------------------- |
+
+
+This course makes use of [GitHub Actions](https://github.com/features/actions), a feature that is currently available for GitHub.com but not available on GHES.
+
+<!-- /end compatibility header -->
+
+### Course dependencies
+
+The following are dependencies of the course. The course may continue to work without these dependencies, but learners won't experience the course as designed.
+
+<!-- this table contains some options, remove (or add) rows as you see necessary for your course -->
+
+| Dependency                                               | Required? | Reason                                                                                                                                           | Alternative                                                                                                                                                                                    |
+| -------------------------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| GHES must be able to reach githubusercontent.com         | Yes       | Images used throughout the course are served from this domain. Learners will find broken images required to take the course without this access. | Manually download the images referenced in the `responses/` folder, upload them to an accessible domain, and replace the images in the `responses/` folder.                                    |
+| Learner must be able to reach github.com and outside web | Yes       | Links are provided to resources that live on the outside web.                                                                                    | Without access to resources on the outside web, learners will reach blocked resources. You can change the links to these resources in the `responses/` folder, and in the template repository. |
+
+|