Test run fixes

Author: FidelusAleksander

.github/steps/1-preparing.md

@@ -55,7 +55,7 @@ Let's start up our development environment, use copilot to learn a bit about the
 
 1. If this is your first time using GitHub Copilot, you will need to accept the usage terms to continue.
 
-1. Enter the below prompt to ask Copilot to introduce you to the project.
+1. Enter the below prompt to ask Copilot to introduce you to the project. Use Copilot **Ask Mode** for this prompt.
 
    > ![Static Badge](https://img.shields.io/badge/-Prompt-text?style=social&logo=github%20copilot)
    >
@@ -98,23 +98,7 @@ Great work! Now that we are familiar with the app and we know it works, let's as
    > ![Static Badge](https://img.shields.io/badge/-Prompt-text?style=social&logo=github%20copilot)
    >
    > ```prompt
-   > Hey copilot, how can I create and publish a new Git branch?
-   > ```
-
-   > **Tip:** This is a simple example, but Copilot is great at providing more tailored commands that might involve loops, pattern matching, file modification, and more! Don't be afraid to ask Copilot for a suggestion. Just remember it is a suggestion and you should always verify it first to be safe.
-
-1. Copilot probably gave us a command like the following. Rather than manually modify it, let's respond back to tell Copilot to use a particular name.
-
-   ```bash
-   git checkout -b {new_branch_name}
-   git push -u origin {new_branch_name}
-   ```
-
-   > ![Static Badge](https://img.shields.io/badge/-Prompt-text?style=social&logo=github%20copilot)
-   >
-   > ```prompt
-   > Awesome! Thanks, Copilot! Let's use the
-   > branch name "accelerate-with-copilot".
+   > Hey copilot, how can I create and publish a new Git branch called "accelerate-with-copilot"?
    > ```
 
    > **Tip:** If Copilot doesn't give you quite what you want, you can always continue explaining what you need. Copilot will remember the conversation history for follow-up responses.

.github/workflows/3-copilot-edits.yml

@@ -67,6 +67,16 @@ jobs:
           minimum-occurrences: 3
           case-sensitive: false
 
+      - name: Check for participant info in styles.css
+        id: check-app-js
+        continue-on-error: true
+        uses: skills/action-keyphrase-checker@v1
+        with:
+          text-file: src/static/styles.css
+          keyphrase: participant
+          minimum-occurrences: 1
+          case-sensitive: false
+
       - name: Update comment - step results
         uses: GrantBirki/[email protected]
         with:
@@ -80,6 +90,8 @@ jobs:
             results_table:
               - description: "Check app.js for participant info"
                 passed: ${{ steps.check-app-js.outcome == 'success' }}
+              - description: "Check styles.css for participant info"
+                passed: ${{ steps.check-styles-css.outcome == 'success' }}
 
       - name: Fail job if not all checks passed
         if: contains(steps.*.outcome, 'failure')
@@ -90,7 +102,8 @@ jobs:
     needs: [find_exercise, check_step_work]
     runs-on: ubuntu-latest
     env:
-      ISSUE_URL: ${{ needs.find_exercise.outputs.issue-url }}
+      ISSUE_REPOSITORY: ${{ github.repository }}
+      ISSUE_NUMBER: ${{ needs.find_exercise.outputs.issue-number }}
 
     steps:
       - name: Checkout
@@ -130,6 +143,5 @@ jobs:
         run: |
           gh workflow disable "${{github.workflow}}"
           gh workflow enable "Step 4"
-          gh workflow enable "Step 4b"
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}