feat: draft migration to issue-based

Author: chriswblake

.github/steps/-step.txt

@@ -1,11 +1,3 @@
-<!--
-  <<< Author notes: Step 1 >>>
-  Choose 3-5 steps for your course.
-  The first step is always the hardest, so pick something easy!
-  Link to docs.github.com for further explanations.
-  Encourage users to open new tabs for steps!
--->
-
 ## Step 1: Open a pull request
 
 _Welcome to "Review pull requests"! :wave:_
@@ -24,4 +16,4 @@ Let's get started by opening a pull request.
 6. Enter a title for your pull request: `Update the game over message`.
 7. Enter a description for your pull request: `Update the game over message so people know how to play again!`
 8. Click **Create pull request**.
-9. Wait about 20 seconds then refresh this page (the one you're following instructions from). [GitHub Actions](https://docs.github.com/en/actions) will automatically update to the next step.
+9. With the pull request created, Mona will check your progress then prepare and share the next steps.

.github/steps/0-welcome.md

@@ -1,10 +1,3 @@
-<!--
-  <<< Author notes: Step 2 >>>
-  Start this step by acknowledging the previous step.
-  Define terms and link to docs.github.com.
-  Historic note: this step combines the commend, approve, and needs changes steps from the previous version.
--->
-
 ## Step 2: Assign yourself
 
 _Great job opening that pull request! :wave:_
@@ -20,4 +13,4 @@ The best way to get a review is to ask for one. On GitHub, you can ask someone t
 
    Because you created the pull request, you can't assign yourself as a reviewer, but feel free to assign a friend as a reviewer instead to see how it works :smile:
 
-1. Wait about 20 seconds then refresh this page (the one you're following instructions from). [GitHub Actions](https://docs.github.com/en/actions) will automatically update to the next step.
+1. With the pull request assigned, Mona will check your progress then prepare and share the next steps.

.github/steps/1-open-a-pull-request.md

@@ -1,10 +1,3 @@
-<!--
-  <<< Author notes: Step 3 >>>
-  Start this step by acknowledging the previous step.
-  Define terms and link to docs.github.com.
-  Historic note: this step combines the commend, approve, and needs changes steps from the previous version.
--->
-
 ## Step 3: Leave a review
 
 _You assigned yourself! :tada:_
@@ -37,4 +30,4 @@ When an approval or request for changes is not yet needed, consider using **comm
 1. Add a comment with your initial thoughts on the pull request.
 1. Select _comment_. You won't be able to _approve_ or _request changes_ to your own pull request.
 1. Click **Submit review**.
-1. Wait about 20 seconds then refresh this page (the one you're following instructions from). [GitHub Actions](https://docs.github.com/en/actions) will automatically update to the next step.
+1. With the review submitted, Mona will check your progress then prepare and share the next steps.

.github/steps/2-assign-yourself.md

@@ -1,9 +1,3 @@
-<!--
-  <<< Author notes: Step 4 >>>
-  Start this step by acknowledging the previous step.
-  Define terms and link to docs.github.com.
--->
-
 ## Step 4: Suggest changes
 
 _Nice work reviewing that pull request :sparkles:_
@@ -22,4 +16,4 @@ Now that you have explored the different ways you can review a pull request it i
    ![add-a-suggestion-button](https://user-images.githubusercontent.com/97056108/184449714-61e8ee51-824a-48c1-9436-2dfd67f2c070.png)
 1. Edit the suggestion.
 1. Click **Add a single comment**.
-1. Wait about 20 seconds then refresh this page (the one you're following instructions from). [GitHub Actions](https://docs.github.com/en/actions) will automatically update to the next step.
+1. With commented added, Mona will check your progress then prepare and share the next steps.

.github/steps/3-leave-a-review.md

@@ -1,9 +1,3 @@
-<!--
-  <<< Author notes: Step 5 >>>
-  Start this step by acknowledging the previous step.
-  Define terms and link to docs.github.com.
--->
-
 ## Step 5: Apply suggested changes
 
 _Nicely done suggesting changes! :partying_face:_
@@ -15,4 +9,4 @@ Now let's see how easy it is to [apply your suggestion](https://docs.github.com/
 1. Click **Commit suggestion**.
 1. Type a commit message.
 1. Click **Commit changes**.
-1. Wait about 20 seconds then refresh this page (the one you're following instructions from). [GitHub Actions](https://docs.github.com/en/actions) will automatically update to the next step.
+1. With the changes committed, Mona will check your progress then prepare and share the next steps.

.github/steps/4-suggest-changes.md

@@ -1,9 +1,3 @@
-<!--
-  <<< Author notes: Step 6 >>>
-  Start this step by acknowledging the previous step.
-  Define terms and link to docs.github.com.
--->
-
 ## Step 6: Merge your pull request
 
 _Almost there! :heart:_
@@ -14,4 +8,4 @@ You can now [merge](https://docs.github.com/en/get-started/quickstart/github-glo
 
 1. Click **Merge pull request**.
 1. Delete the branch `update-game` (optional).
-1. Wait about 20 seconds then refresh this page (the one you're following instructions from). [GitHub Actions](https://docs.github.com/en/actions) will automatically update to the next step.
+1. With the pull request merged, Mona will check your progress and prepare a file review. Congrats you are done! 🎉

.github/steps/5-apply-changes.md

@@ -1,9 +1,4 @@
-<!--
-  <<< Author notes: Finish >>>
-  Review what we learned, ask for feedback, provide next steps.
--->
-
-## Finish
+## Review
 
 _Congratulations friend, you've completed this course!_
 

.github/steps/6-merge-your-pull-request.md

@@ -0,0 +1,104 @@
+name: Step 0
+
+on:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: write
+  actions: write
+  issues: write
+
+env:
+  STEP_1_FILE: ".github/steps/1-open-a-pull-request.md"
+
+jobs:
+  start_exercise:
+    if: |
+      !github.event.repository.is_template
+    name: Start Exercise
+    uses: skills/exercise-toolkit/.github/workflows/[email protected]
+    with:
+      exercise-title: "Review Pull Requests"
+      intro-message: "Let's learn to collaborate with others using pull requests."
+
+  modify_repo_content:
+    name: Modify repo content
+    runs-on: ubuntu-latest
+    needs: [start_exercise]
+    env:
+      ISSUE_URL: ${{ needs.start_exercise.outputs.issue-url }}
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Prepare a branch and pull request
+        run: |
+
+          echo "Make a branch"
+          BRANCH=update-game
+          git checkout -b $BRANCH
+
+          echo "Update index.html"
+          sed -i.bak 's/Game over/Game over, refresh to play again 🧑‍💻 🤖!/' index.html
+
+          echo "Make a commit"
+          git config user.name github-actions[bot]
+          git config user.email github-actions[bot]@users.noreply.github.com
+          git add index.html
+          git commit --message="Update game over message"
+
+          echo "Push"
+          git push --set-upstream origin $BRANCH
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+  post_next_step_content:
+    name: Post next step content
+    runs-on: ubuntu-latest
+    needs: [start_exercise]
+    env:
+      ISSUE_URL: ${{ needs.start_exercise.outputs.issue-url }}
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Get response templates
+        uses: actions/checkout@v4
+        with:
+          repository: skills/exercise-toolkit
+          path: exercise-toolkit
+          ref: v0.5.0
+
+      - name: Build comment - add step content
+        id: build-comment
+        uses: skills/action-text-variables@v2
+        with:
+          template-file: ${{ env.STEP_1_FILE }}
+          template-vars: |
+            login: ${{ github.actor }}
+            full_repo_name: ${{ github.repository }}
+
+      - name: Create comment - add step content
+        run: |
+          gh issue comment "$ISSUE_URL" \
+            --body "$ISSUE_BODY"
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          ISSUE_BODY: ${{ steps.build-comment.outputs.updated-text }}
+
+      - name: Create comment - watching for progress
+        run: |
+          gh issue comment "$ISSUE_URL" \
+            --body-file "exercise-toolkit/markdown-templates/step-feedback/watching-for-progress.md"
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Enable next step workflow
+        run: |
+          gh workflow enable "Step 1"
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}