Add next step prompt

hollenberry · hollenberry · commit 4a81d305e3d7 · 2019-01-24T19:08:55.000-08:00
diff --git a/responses/add-context.md b/responses/add-context.md
@@ -10,3 +10,6 @@ We'll add the `left:` option to the gate, and set it to the pull request's title
 1. Set the gate's `right:` to the title we expect which is `Add name to README`
 
 You can also accept the suggested changes below. They're in batch, so you'll have to go to Files Changed.
+
+<hr>
+<h3 align="center">I'll respond below with your next step.</h3>
diff --git a/responses/add-descriptions.md b/responses/add-descriptions.md
@@ -3,3 +3,6 @@ Remember your course's metadata, near the top of your config? We left the descri
 ### :keyboard: Activity: Accept the suggested changes
 
 Click `Accept suggested change` below or change the lines manually.
+
+<hr>
+<h3 align="center">I'll respond below with your next step.</h3>
diff --git a/responses/add-first-step.md b/responses/add-first-step.md
@@ -1,5 +1,8 @@
-Great! The learner's repo will now be setup. Let's now dive into the `steps:`. This block is composed of steps that are triggered by `events` on GitHub, and in turn certain `actions` take place. 
+Great! The learner's repo will now be setup. Let's now dive into the `steps:`. This block is composed of steps that are triggered by `events` on GitHub, and in turn certain `actions` take place.
 
 Note: `actions` in this context is NOT the same as GitHub Actions.
 
-Let's name our first step. 
+Let's name our first step.
+
+<hr>
+<h3 align="center">I'll respond below with your next step.</h3>
diff --git a/responses/add-readme.md b/responses/add-readme.md
@@ -3,3 +3,6 @@ The last thing that remains is a README. This file is show no the course's page,
 ### :keyboard: Activity: Edit the README.md
 
 - We added a README for you, but go ahead and put in your own content.
+
+<hr>
+<h3 align="center">I'll respond below with your next step.</h3>
diff --git a/responses/add-repo-name.md b/responses/add-repo-name.md
@@ -3,3 +3,6 @@ Awesome! The learner's repository will now be cloned from `lab-starter-template`
 ### :keyboard: Activity: Update the repository name
 
 Change the field `name:` as part of the `template:` section to anything you like. You can also accept the suggestion below.
+
+<hr>
+<h3 align="center">I'll respond below with your next step.</h3>
diff --git a/responses/add-response.md b/responses/add-response.md
@@ -5,3 +5,6 @@ Great, we referenced a file title `welcome-text.md`, but it doesn't exist. Learn
 1. In the `/responses/` folder, create a new file titled `welcome-text.md`
 1. In that file, add some content that will appear to the learner in the welcome issue.
 1. Add an instruction for the learner to open a new PR titled "Add name to README" in which they add their name to the README file.
+
+<hr>
+<h3 align="center">I'll respond below with your next step.</h3>
diff --git a/responses/add-template.md b/responses/add-template.md
@@ -7,3 +7,7 @@ Let's add our own template repo. To speed things up, we've created a template re
 You can edit the file directly or accept the suggested change below.
 
 ### :keyboard: Activity: Add a template repo
+
+
+<hr>
+<h3 align="center">I'll respond below with your next step.</h3>
diff --git a/responses/add-title.md b/responses/add-title.md
@@ -3,3 +3,7 @@ Great! You opened the PR.
 Now let's give your course a title. You can do so by editing `config.yml` directly and changing the title field, or accepting the suggestion below.
 
 ### :keyboard: Activity: Give your course a title
+
+
+<hr>
+<h3 align="center">I'll respond below with your next step.</h3>
diff --git a/responses/add-trigger.md b/responses/add-trigger.md
@@ -1,3 +1,6 @@
 Great! Your learner now has information about what they're expected to do in this step of the course.
 
-Let's now find the `event` that will trigger the step. Because we want the learner to open a new Pull Request, the event we're looking for is `pull_request.opened`.
+Let's now find the `event` that will trigger the step. Because we want the learner to open a new Pull Request, the event we're looking for is `pull_request.opened`.
+
+<hr>
+<h3 align="center">I'll respond below with your next step.</h3>
diff --git a/responses/create-issue.md b/responses/create-issue.md
@@ -7,3 +7,6 @@ We'll use the `createIssue` action to create an issue for the learner with some
 We'll define both of those here, but we'll create the body in the next step. You can edit the file manually or accept the suggested changes below. Since there are multiple suggested changes, you can go to the "Files changed tab" and accept them as a batch.
 
 ### :keyboard: Activity:
+
+<hr>
+<h3 align="center">I'll respond below with your next step.</h3>
diff --git a/responses/publish.md b/responses/publish.md
@@ -7,3 +7,6 @@ Your course is now complete! Let's publish it.
 1. Navigate to https://lab-sandbox.github.com/{{ owner }}/new.
 1. In the Repository name field, type in **{{ repo }}**
 1. We recommend selecting **Private** so you can test the course with other members of the organization before making it public.
+
+<hr>
+<h3 align="center">I'll respond below with your next step.</h3>
diff --git a/responses/respond-success.md b/responses/respond-success.md
@@ -10,3 +10,6 @@ Let's respond to the learner letting them know they've completed our course upon
 We created the response file for you but feel free to change it.
 
 You can also accept the suggested changes below.
+
+<hr>
+<h3 align="center">I'll respond below with your next step.</h3>
diff --git a/responses/validate.md b/responses/validate.md
@@ -5,3 +5,6 @@ The action that will help us validate the learner's PR is a `gate`. Gates are co
 ### :keyboard: Activity: Adding a gate
 
 1. Add a gate or accept the suggested change below.
+
+<hr>
+<h3 align="center">I'll respond below with your next step.</h3>
diff --git a/responses/welcome.md b/responses/welcome.md
@@ -5,3 +5,6 @@ However, we need to fill in some of the fields. I've started a branch with the f
 ### :keyboard: Activity: Open a PR
 
 1. [Open a pull request]({{ prUrl }}) against `add-metadata`.
+
+<hr>
+<h3 align="center">I'll respond in your new pull request with your next step.</h3>
