Trigger step checks on merge to main to avoid Actions approval

.github/steps/1-step.md

@@ -18,12 +18,14 @@ GitHub Copilot Spaces enables teams to centralize and democratize organizational
 To get started, you need access to Copilot Spaces and a GitHub Copilot plan with premium request units. Each prompt in a Space counts toward your usage quota, so be mindful of your plan's limits. For more details, see [GitHub Copilot plans](https://docs.github.com/en/copilot/get-started/plans#comparing-copilot-plans) and [Copilot Requests](https://docs.github.com/en/copilot/concepts/billing/copilot-requests).
 
 > [!IMPORTANT]
-> If you are using a Copilot free plan or are concerned with impacting usage based billing, use "**Auto**". These models do not consume premium request units. For more information, see [GitHub Copilot plans](https://docs.github.com/en/copilot/get-started/plans#comparing-copilot-plans, [Usage Based Billing for individuals](https://docs.github.com/en/copilot/concepts/billing/usage-based-billing-for-individuals), and [Usage Based Billing for Enterprises and Organizations](https://docs.github.com/en/copilot/concepts/billing/usage-based-billing-for-organizations-and-enterprises).
+> If you are using a Copilot free plan or are concerned with impacting usage based billing, use "**Auto**". These models do not consume premium request units. For more information, see [GitHub Copilot plans](https://docs.github.com/en/copilot/get-started/plans#comparing-copilot-plans), [Usage Based Billing for individuals](https://docs.github.com/en/copilot/concepts/billing/usage-based-billing-for-individuals), and [Usage Based Billing for Enterprises and Organizations](https://docs.github.com/en/copilot/concepts/billing/usage-based-billing-for-organizations-and-enterprises).
 
-> [!IMPORTANT]
-> Before starting this GitHub Skills exercise make sure
-> **Settings** --> **Actions** --> **General** (part way down) shown in the following image
-> "**Require approval for first-time contributors who are new to GitHub**"
+> [!NOTE]
+> **Optional:** This exercise now advances automatically when you merge your pull
+> request, so you do not need to change any approval settings to progress.
+> If you prefer, you can still review **Settings** --> **Actions** --> **General**
+> (part way down) --> "**Require approval for first-time contributors who are new to GitHub**"
+> shown in the following image, but it is not required for this exercise.
 
 <img width="50%" alt="copilot-spaces-create-space" src="../images/settings-actions-general-approvals.png" />
 
@@ -149,5 +151,7 @@ You can copy or open the link in a new tab to see the newly created issue
 - Make sure you have access to GitHub Copilot Spaces and that your repository is added as a source
 - The repository should be publicly accessible for Copilot to index it
 - Repository indexing can take seconds to minutes depending on size
+- **Conversation clears when you press Send?** Reload the page and try again, or use the **Retry** button. This is usually a transient Copilot Spaces UI issue.
+- If the message keeps disappearing, confirm you have access to Copilot Spaces and, on a free plan, select **Auto** or another model that does not consume premium request units before sending.
 
 </details>

.github/steps/2-step.md

@@ -153,5 +153,6 @@ In this activity, you will connect the issue you created in Step 1 to your Copil
 - **Issue not attaching?** Make sure you're using the exact format `@{{full_repo_name}}/issues/#` where `#` is your issue number
 - **Copilot Cloud Agent not working?** Ensure you have the necessary permissions to create pull requests in your repository
 - **Pull request creation failed?** The issue must be properly attached before the Copilot Cloud Agent can work on it
+- **Step didn't advance after merging?** The check runs automatically when the pull request is merged into `main`. Give it a moment, then open the [Actions tab](https://github.com/{{full_repo_name}}/actions) to confirm the **Step 2** run completed. No manual approval is required
 
 </details>

.github/steps/3-step.md

@@ -176,5 +176,6 @@ In the same Copilot Space conversation do the following:
 - Consider adding templates, checklists, or clarifying existing processes
 - Common improvements include: role clarification, communication protocols, decision-making frameworks
 - Even small improvements like adding examples or clarifying steps can be valuable
+- **Step didn't complete after merging?** The check runs automatically when the pull request is merged into `main`. Give it a moment, then open the [Actions tab](https://github.com/{{full_repo_name}}/actions) to confirm the **Step 3** run completed. No manual approval is required
 
 </details>

.github/workflows/2-step.yml

@@ -1,11 +1,9 @@
 name: Step 2
 
 on:
-  pull_request:
+  push:
     branches:
       - main
-    types:
-      - closed
     paths:
       - "docs/**"
 

.github/workflows/3-last-step.yml

@@ -1,11 +1,9 @@
 name: Step 3 # Last step of the exercise
 
 on:
-  pull_request:
+  push:
     branches:
       - main
-    types:
-      - closed
     paths:
       - "docs/**"
 

README.md

@@ -63,6 +63,8 @@ If the exercise isn't ready in 20 seconds, please check the [Actions](../../acti
 
 - If the page shows a failed job, please submit an issue. Nice, you found a bug! 🐛
 
+- Steps advance automatically when you merge your pull request into `main`; no manual workflow approval is required. If a step seems delayed, check the [Actions](../../actions) tab to confirm the run completed.
+
 </details>
 
 ---