clean up the first step a bit

Author: hectorsector

config.yml

@@ -11,8 +11,24 @@ tags:
 template:
   repo: write-github-script-template
   name: write-github-script
+
+# Repo artifacts
+#       repositoryUrl
+# 1. (Issue) Start here!
+#       welcomeIssueUrl
+#       welcomeIssueNumber
+# 2. (PR) Learner created PR, "Automate issue response" possibly
+#       firstPullNumber
+#       firstPullUrl
+# 3. (Issue) Create an issue comment with GitHub Script
+#       secondIssueNumber
+#       secondIssueUrl
+
 before:
   - type: updateBranchProtection
+    store:
+      repositoryUrl: '{{ payload.repository.html_url }}'
+      actionsUrl: '{{ payload.repository.html_url }}/actions'
   - type: createProjectBoard
     name: Learning Lab Project Board
     description: >-
@@ -29,8 +45,8 @@ before:
       welcomeIssueUrl: "%result.data.html_url%"
       welcomeIssueNumber: "%result.data.number%"
     data:
-      quicklink: "%payload.repository.html_url%/new/master?filename=.github/workflows/my-workflow.yml"
-      actionsUrl: "%payload.repository.html_url%/actions/new"
+      quicklink: "{{ store.repositoryUrl }}/new/master?filename=.github/workflows/my-workflow.yml"
+      actionsUrl: "{{ store.repositoryUrl }}/actions/new"
     comments:
       - 00_explain-gh-script.md
       - 00_octokit-comparison.md
@@ -44,28 +60,16 @@ steps:
       - pull_request.edited
     link: "{{store.welcomeIssueUrl}}"
     actions:
-      - type: gate
-        left: "%payload.pull_request.title%"
-        store:
-          firstPullNumber: "%payload.pull_request.number%"
-          firstPullUrl: "%payload.pull_request.html_url%"
-        operator: ===
-        right: Automate issue responses
-
-        # if those statments FAIL... do this
-        else:
-          - type: respond
-            with: e-rename-pr.md
-            data:
-              title: Automate issue responses
-        # if those gates === true Then do this stuff
-      #######################################################
       # Validate the filepath for the my-workflow.yml file
       # get tree
       - type: getTree
         action_id: isInTree
         recursive: true
         sha: "%payload.pull_request.head.sha%"
+        store:
+          firstPullNumber: "%payload.pull_request.number%"
+          firstPullUrl: "%payload.pull_request.html_url%"
+
       # check for a file in a tree
       - type: gate
         left: "%actions.isInTree.data.tree%"

responses/00_welcome-activity.md

@@ -49,14 +49,18 @@ Your repository can contain multiple **workflow** files that carry out a wide va
    ```
 
 1. Commit the workflow to a new branch.
-1. Create a pull request titled **Automate issue responses**.
+1. Create a pull request. I suggest a title like **Automate issue responses**.
 1. Supply the pull request body content and click `Create pull request`.
 
-_It is important to place meaningful content into the body of the pull requests you create throughout this course. This repository will stay with you long after you complete the course. It is advisable that you use the body of the pull requests you create as a way to take long lived notes about thing you want to remember._
+<details><summary>About pull pull request titles and content</summary>
 
-<details><summary>Suggested body content</summary>
+It is important to place meaningful content into the body of the pull requests you create. This repository will stay with you long after you complete the course. We recommend you use the body of your pull requests as a way to take long lived notes about thing you want to remember.
 
-`Workflow files are the recipe for task automation. This is where actions are placed if I want to use them for a task.`
+In practice, good pull request titles and content convey information efficiently to your collaborators.
+
+You can fill the body of this pull request with the following recommended content:
+
+> Workflow files are the recipe for task automation. This is where actions are placed if I want to use them for a task.
 
 </details>