Merge pull request #40 from githubtraining/use-store-for-links

Use `store` to track step links

Author: mattdavis0351

config.yml

@@ -17,7 +17,9 @@ before:
     title: There's a bug!
     body: 00_bug.md
     data:
-      actionsUrl: "%payload.repository.html_url%/actions/new"
+      actionsUrl: "{{ payload.repository.html_url }}/actions/new"
+    store:
+      first_issue_url: "{{ result.data.html_url }}"
 
 # Repository artifacts
 # 1. Issue: There's a bug!
@@ -35,7 +37,7 @@ steps:
   - title: Use a templated workflow
     description: Create a pull request with a templated workflow
     event: pull_request
-    link: "{{ repoUrl }}/issues/1"
+    link: "{{ store.first_issue_url }}"
     actions:
       - type: gate
         gates:
@@ -54,6 +56,8 @@ steps:
             with: e-rename-pr.md
             data:
               title: CI for Node
+        store:
+          ci_for_node_pr: "{{ payload.pull_request.number }}"
       - type: respond
         with: 01_explain-template.md
         data:
@@ -79,14 +83,16 @@ steps:
         body: 01_merge-jest.md
         base: "%payload.pull_request.head.ref%"
         head: add-jest
+        store:
+          second_pr_url: "{{ result.data.html_url }}"
 
   # Step 2
   # 1. GitHub sends us a workflow run.
   # 1. Bot explains what is happening, and why the page build failed (we don't have a [test script](https://github.com/githubtraining/actions-template/blob/master/package.json#L10))
   - title: Run a templated workflow
     description: Wait for GitHub to run the templated workflow and report back the results
     event: check_suite.completed
-    link: "{{ repoUrl }}/pull/2"
+    link: "{{ store.second_pr_url }}"
     actions:
       - type: gate
         left: "%payload.check_suite.app.slug%"
@@ -109,7 +115,7 @@ steps:
   - title: Add your first test
     description: Add your first test script for CI to pick up
     event: pull_request.synchronize
-    link: "{{ repoUrl }}/pull/2"
+    link: "{{ store.second_pr_url }}"
     actions:
       - type: respond
         with: 03_wait-for-first-test.md
@@ -128,7 +134,7 @@ steps:
   - title: Read an Actions log
     description: Tell the bot which test is failing so we can fix it
     event: issue_comment.created
-    link: "{{ repoUrl }}/pull/2"
+    link: "{{ store.second_pr_url }}"
     actions:
       - type: gate
         left: "/(Initializes with two players)|(Starts the game with a random player)|(Sets the current player to be whoever it is not)/gim"
@@ -139,7 +145,7 @@ steps:
           - type: respond
             with: e-test-name.md
       - type: getPullRequest
-        pullRequest: CI for Node
+        pullRequest: "{{ store.ci_for_node_pr }}"
         action_id: ciPr
       - type: respond
         with: 04_read-failed-log.md
@@ -162,7 +168,7 @@ steps:
   - title: Fix the test
     description: Edit the file that's causing the test to fail
     event: check_suite.completed
-    link: "{{ repoUrl }}/pull/2"
+    link: "{{ store.second_pr_url }}"
     actions:
       - type: gate
         left: "%payload.check_suite.app.slug%"
@@ -196,7 +202,7 @@ steps:
   - title: Share the workflow with the team
     description: Merge the pull request containing your first workflow so the entire team can use it
     event: pull_request.closed
-    link: "{{ repoUrl }}/pull/2"
+    link: "{{ store.second_pr_url }}"
     actions:
       - type: gate
         every: true
@@ -210,7 +216,9 @@ steps:
         body: 06_custom-workflow.md
         action_id: newIssue
         data:
-          workflowUrl: "%payload.repository.html_url%/edit/master/.github/workflows/node.js.yml"
+          workflowUrl: "%payload.repository.html_url%/edit/master/.github/workflows/nodejs.yml"
+        store:
+          workflow_issue_url: "{{ result.data.html_url }}"
       - type: respond
         with: 0X_goto.md
         data:
@@ -222,7 +230,7 @@ steps:
   - title: Create a custom GitHub Actions workflow
     description: Edit the existing workflow with new build targets
     event: pull_request
-    link: "{{ repoUrl }}/pull/5"
+    link: "{{ store.workflow_issue_url }}"
     actions:
       - type: gate
         gates:
@@ -258,15 +266,17 @@ steps:
         file: .github/workflows/node.js.yml
         body: 07_add-windows.md
         data:
-          fileUrl: "%payload.repository.html_url%/edit/%payload.pull_request.head.ref%/.github/workflows/node.js.yml?pr=/%payload.repository.full_name%/pull/%payload.number%"
+          fileUrl: "%payload.repository.html_url%/edit/%payload.pull_request.head.ref%/.github/workflows/nodejs.yml?pr=/%payload.repository.full_name%/pull/%payload.number%"
+        store:
+          node_version_pr: "{{ payload.pull_request.html_url }}"
 
   # Step 8
   # 1. Learner adds Windows to the [matrix os](https://github.com/githubtraining/actions-template/blob/master/.github/workflows/node.js.yml#L9)
   # 1. Bot asks learner to add a new job for testing, and separate out the test script into that new job.
   - title: Target a Windows environment
     description: Edit your workflow file to build for Windows environments
     event: pull_request.synchronize
-    link: "{{ repoUrl }}/pull/5"
+    link: "{{ store.node_version_pr }}"
     actions:
       # - type: findInTree
       #   path: .github/workflows/node.js.yml
@@ -288,7 +298,7 @@ steps:
   - title: Use multiple jobs
     description: Edit your workflow file to separate build and test jobs
     event: pull_request.synchronize
-    link: "{{ repoUrl }}/pull/5"
+    link: "{{ store.node_version_pr }}"
     actions:
       # - type: findInTree
       #   path: .github/workflows/node.js.yml
@@ -311,7 +321,7 @@ steps:
   - title: Run multiple jobs
     description: Wait for the result of multiple jobs in your workflow
     event: check_suite.completed
-    link: "{{ repoUrl }}/pull/5"
+    link: "{{ store.node_version_pr }}"
     actions:
       - type: gate
         left: "%payload.check_suite.app.slug%"
@@ -337,7 +347,7 @@ steps:
   - title: Upload a job's build artifacts
     description: Use the upload action in your workflow file to save a job's build artifacts
     event: pull_request.synchronize
-    link: "{{ repoUrl }}/pull/5"
+    link: "{{ store.node_version_pr }}"
     actions:
       # - type: findInTree
       #   path: .github/workflows/node.js.yml
@@ -367,7 +377,7 @@ steps:
   - title: Download a job's build artifacts
     description: Use the download action in your workflow file to access a prior job's build artifacts
     event: pull_request.synchronize
-    link: "{{ repoUrl }}/pull/5"
+    link: "{{ store.node_version_pr }}"
     actions:
       # - type: findInTree
       #   path: .github/workflows/node.js.yml
@@ -386,7 +396,7 @@ steps:
   # Step 13
   - title: Share the improved CI workflow with the team
     description: Merge the pull request with the improved workflow
-    link: "{{ repoUrl }}/pull/5"
+    link: "{{ store.node_version_pr }}"
     event: pull_request.closed
     actions:
       - type: gate
@@ -399,17 +409,16 @@ steps:
       - type: mergeBranch
         head: master
         base: team-workflow
-      - type: getIssue
-        issue: A workflow for the entire team
-        action_id: workflow
       - type: createPullRequest
         title: A custom workflow
         body: 13_partial-workflow.md
         head: team-workflow
         action_id: newPR
         data:
-          workflowIssue: "%actions.workflow.data.html_url%"
+          workflowIssue: "{{ store.workflow_issue_url }}"
           fileUrl: "%payload.repository.html_url%/new/team-workflow/?filename=.github/workflows/approval-workflow.yml"
+        store:
+          workflow_pr_url: "{{ result.data.html_url }}"
       - type: respond
         with: 0X_goto.md
         data:
@@ -422,7 +431,7 @@ steps:
   # 1. Bot asks the learner to choose an event, explains how those events trigger the workflow
   - title: Automate the review process
     description: Add a new workflow file to automate the team's review process
-    link: "{{ repoUrl }}/pull/6"
+    link: "{{ store.workflow_pr_url }}"
     event: pull_request.synchronize
     actions:
       - type: gate
@@ -443,7 +452,7 @@ steps:
   # 1. Bot asks learner to add a job with their own title, explains what that does
   - title: Use an action to automate pull request reviews
     description: Use the community action in your new workflow
-    link: "{{ repoUrl }}/pull/6"
+    link: "{{ store.workflow_pr_url }}"
     event: pull_request.synchronize
     actions:
       - type: gate
@@ -464,7 +473,7 @@ steps:
   # 1. Bot asks learner to choose a virtual environment, bot explains environment options and why we'd like to pick a specific one
   - title: Create an approval job in your new workflow
     description: In your new workflow file, create a new job that'll use the community action
-    link: "{{ repoUrl }}/pull/6"
+    link: "{{ store.workflow_pr_url }}"
     event: pull_request.synchronize
     actions:
       - type: gate
@@ -483,7 +492,7 @@ steps:
   # 1. Bot points out that branch protections aren't currently in place, asks learner to set branch protections, and approve the PR
   - title: Automate approvals
     description: Use the community action to automate part of the review approval process
-    link: "{{ repoUrl }}/pull/6"
+    link: "{{ store.workflow_pr_url }}"
     event:
       - pull_request.synchronize
       - issue_comment.created
@@ -521,7 +530,7 @@ steps:
   # 1. Bot turns on pages build, drops link in the PR, explains to the learner the value on a workflow that enforces team behaviors.
   - title: Use branch protections
     description: Complete the automated review process by protecting the master branch
-    link: "{{ repoUrl }}/pull/6"
+    link: "{{ store.workflow_pr_url }}"
     event:
       - pull_request_review.submitted
       - pull_request.labeled