From abe50b887a4f4a9f2a0785585f464ede7aa1c58d Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 20 Jul 2026 20:09:37 +0000 Subject: [PATCH 1/3] Initial plan From 383cd3a0c6df2293db0f2d1f27af8627eb2dfb0e Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 20 Jul 2026 20:11:58 +0000 Subject: [PATCH 2/3] Add browser/CCA compile fallback in Step 12 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- workshop/12-test-and-iterate.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/workshop/12-test-and-iterate.md b/workshop/12-test-and-iterate.md index 0826bc10..57643ff6 100644 --- a/workshop/12-test-and-iterate.md +++ b/workshop/12-test-and-iterate.md @@ -60,6 +60,18 @@ If the compiler reports an error, fix that first. Do not start a new test run un > [!TIP] > If you expect to make several small edits in a row, `gh aw compile --watch` can speed up the loop by recompiling after each save. +## If You Cannot Run the Terminal + +If you are using GitHub Copilot Cloud Agent (CCA) or working from mobile, ask Copilot to compile for you: + +```text +Ask Copilot to compile the workflow and commit the updated lock file. +``` + +Then review the commit and confirm your workflow `.lock.yml` file changed before you trigger the next run. + +If you want a guided browser-first loop, use [Side Quest: Evaluating and Iterating on Agent Output](side-quest-12-01-iterate-agent-output.md), which includes a Copilot agent path for running `gh aw compile` without using your own terminal. + ## Commit Both Workflow Files After `gh aw compile` succeeds, commit both the source workflow and the regenerated lock file: @@ -92,6 +104,7 @@ If you want a stricter review loop, score each run for accuracy, completeness, a - [ ] I changed only one instruction or configuration detail before testing again - [ ] I ran `gh aw compile` after the edit and before triggering the next run - [ ] I committed both the workflow `.md` file and the regenerated `.lock.yml` file +- [ ] If I used a browser or Copilot agent path, I confirmed the latest commit updated the `.lock.yml` file - [ ] I compared the new run with the previous run and decided what to change next From 8528fffcc92b480ab7c402dda4e540ba4b93b1e8 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 20 Jul 2026 20:12:40 +0000 Subject: [PATCH 3/3] Clarify Copilot compile prompt in Step 12 fallback Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- workshop/12-test-and-iterate.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/workshop/12-test-and-iterate.md b/workshop/12-test-and-iterate.md index 57643ff6..680ca6d3 100644 --- a/workshop/12-test-and-iterate.md +++ b/workshop/12-test-and-iterate.md @@ -65,12 +65,12 @@ If the compiler reports an error, fix that first. Do not start a new test run un If you are using GitHub Copilot Cloud Agent (CCA) or working from mobile, ask Copilot to compile for you: ```text -Ask Copilot to compile the workflow and commit the updated lock file. +Please run `gh aw compile` and commit both the workflow `.md` file and the regenerated `.lock.yml` file. ``` Then review the commit and confirm your workflow `.lock.yml` file changed before you trigger the next run. -If you want a guided browser-first loop, use [Side Quest: Evaluating and Iterating on Agent Output](side-quest-12-01-iterate-agent-output.md), which includes a Copilot agent path for running `gh aw compile` without using your own terminal. +For a guided browser-first approach, use [Side Quest: Evaluating and Iterating on Agent Output](side-quest-12-01-iterate-agent-output.md), which includes a Copilot agent workflow for this loop. ## Commit Both Workflow Files