You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: workshop/06c-install-ui.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@
7
7
8
8
## 🎯 What You'll Do
9
9
10
-
You'll confirm that the GitHub UI path does not require a local `gh-aw` installation and proceed directly to authoring your first workflow in the browser.
10
+
You'll confirm that the GitHub UI path does not require a local `gh-aw` installation and proceed to the browser-based GitHub Copilot authoring path.
11
11
12
12
## 📋 Before You Start
13
13
@@ -17,24 +17,24 @@ You'll confirm that the GitHub UI path does not require a local `gh-aw` installa
17
17
18
18
## Why no installation is needed
19
19
20
-
The compiled `.lock.yml` file is what GitHub actually runs. In Step 7b you'll paste the complete [compiled workflow](https://github.github.com/gh-aw/reference/compilation-process/) directly into the web editor — no local compile step needed. GitHub's infrastructure then executes the compiled workflow when you trigger it from the Actions tab.
20
+
The compiled `.lock.yml` file is what GitHub actually runs. In Step 7 you'll ask GitHub Copilot or the repository's **Agents** tab to create and validate the workflow in a browser-based session, so no local compile step is needed. GitHub's infrastructure then executes the committed workflow files when you trigger them from the Actions tab.
21
21
22
22
23
23
24
-
You'll author workflow files using the GitHub web editor in Step 7b and trigger them from the Actions tab in Step 8. You'll confirm `gh-aw` is working when **Daily Report Status** appears in your workflow list.
24
+
You'll author workflow files with GitHub Copilot or the repository's **Agents** tab in Step 7c and trigger them from the Actions tab in Step 8. You'll confirm `gh-aw` is working when **Daily Report Status** appears in your workflow list.
25
25
26
26
## Triggering your workflow from the browser
27
27
28
28
CCA and mobile learners are already authenticated — you signed in to GitHub to reach this step. No additional authentication or terminal is needed.
29
29
30
-
After you commit a workflow file in [Step 7b](07b-your-first-workflow-ui.md) or a later step, navigate to the **Actions** tab in your repository, select the workflow name in the sidebar, and click **Run workflow**. You do not need `gh aw run`.
30
+
After you merge the workflow pull request from [Step 7c](07c-your-first-workflow-copilot.md) or complete a later browser-first step, navigate to the **Actions** tab in your repository, select the workflow name in the sidebar, and click **Run workflow**. You do not need `gh aw run`.
31
31
32
32
If you want a browser-only scenario with no terminal, [Adventure E in Step 10](10-choose-your-scenario.md#adventure-e-browser-only-daily-status-workflow-for-cca-and-mobile) walks you through using the Agentic Workflows agent (Copilot app or Agents tab) to create, compile, and commit a daily status workflow — no terminal required at any stage.
33
33
34
34
## What to do next
35
35
36
36
<!-- journey: ui -->
37
-
Continue to [Write Your First Agentic Workflow — GitHub UI Path](07b-your-first-workflow-ui.md).
37
+
Continue to [Write Your First Agentic Workflow — GitHub Copilot Path](07c-your-first-workflow-copilot.md).
38
38
<!-- /journey -->
39
39
40
40
## ✅ Checkpoint
@@ -46,7 +46,6 @@ Continue to [Write Your First Agentic Workflow — GitHub UI Path](07b-your-firs
46
46
-[ ] You know that CCA and mobile learners can trigger workflows from the **Actions** tab without `gh aw run`
47
47
48
48
<!-- journey: ui -->
49
-
**Next:**[Write Your First Agentic Workflow — GitHub UI Path](07b-your-first-workflow-ui.md)
49
+
**Next:**[Write Your First Agentic Workflow — GitHub Copilot Path](07c-your-first-workflow-copilot.md)
Copy file name to clipboardExpand all lines: workshop/07-your-first-workflow.md
+8-9Lines changed: 8 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,28 +8,27 @@ _Writing your first workflow is the moment theory becomes practice — let's mak
8
8
9
9
You'll create `.github/workflows/daily-report-status.md`, a small workflow that reads repository issues and posts one controlled response.
10
10
11
+
In either path, you'll start with `daily-report-status.md` and end with `daily-report-status.lock.yml`, the compiled workflow that GitHub Actions runs.
12
+
13
+
14
+
11
15
## 📋 Before You Start
12
16
13
17
- Completed [Install the gh-aw CLI Extension](06-install-gh-aw.md)
14
-
- The `gh aw` command is available in your terminal (or you'll use the GitHub UI path)
15
-
- If you are using Terminal or Copilot paths, `gh aw init` has been run and pushed in your practice repository
18
+
- You can use `gh aw` in a terminal or open GitHub Copilot for a browser-based session
16
19
17
20
## Choose Your Path
18
21
19
22
| Path | What you'll do | Continue |
20
23
|---|---|---|
21
24
|**Terminal path**| Build the workflow incrementally in two short parts, compile after each meaningful change, then commit and push |[Write the workflow with the Terminal path](07a-your-first-workflow-terminal.md)|
22
-
|**GitHub Copilot path**| Ask an agent to create and validate the workflow, then review and merge its pull request |[Write the workflow with GitHub Copilot](07c-your-first-workflow-copilot.md)|
25
+
|**GitHub Copilot path**| Ask an agent in GitHub Copilot or the repository's **Agents** tab to create and validate the workflow, then review and merge its pull request |[Write the workflow with GitHub Copilot](07c-your-first-workflow-copilot.md)|
23
26
24
-
The Terminal path gives you early compiler feedback. The GitHub UI path skips local compile checkpoints and uses the **Agentic Workflows** agent in the **Agents** tab to generate the lock file. The GitHub Copilot path delegates `gh aw compile` to the agent's session workspace.
27
+
The Terminal path gives you early compiler feedback. The GitHub Copilot path delegates `gh aw compile` to the agent's session workspace, so browser-first learners can still complete this step without a local terminal.
25
28
26
29
<!-- journey: codespace,local,terminal -->
27
30
Continue with [Write Your First Agentic Workflow — Terminal Path](07a-your-first-workflow-terminal.md).
28
31
<!-- /journey -->
29
-
<!-- journey: copilot -->
32
+
<!-- journey: ui,copilot -->
30
33
Continue with [Write Your First Agentic Workflow — GitHub Copilot Path](07c-your-first-workflow-copilot.md).
31
34
<!-- /journey -->
32
-
33
-
Copy file name to clipboardExpand all lines: workshop/08-run-your-workflow.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ Open your practice repository in GitHub and click **Actions** in the top navigat
31
31
32
32
33
33
34
-
Click **Run workflow**, keep the default branch selected, and click the green **Run workflow** button. If **Daily Report Status** is missing, refresh the page and confirm both workflow files are on `main`. If you used the GitHub UI path, go back to [Step 7b](07b-your-first-workflow-ui.md) and use the **Agentic Workflows** agent to compile the lock file. If you used the Terminal path, run `gh aw compile` to check for compile errors.
34
+
Click **Run workflow**, keep the default branch selected, and click the green **Run workflow** button. If **Daily Report Status** is missing, refresh the page and confirm both workflow files are on `main`. If you used the GitHub Copilot path, return to [Step 7c](07c-your-first-workflow-copilot.md) and confirm the workflow pull request was merged. If you used the Terminal path, run `gh aw compile` to check for compile errors.
35
35
36
36
If the run fails immediately with a model-access or authentication error, return to [Step 7d](07d-confirm-model-access.md) and confirm the selected billing method matches the workflow.
37
37
@@ -64,4 +64,3 @@ Wait for the run to turn green with a ✅. Then open the **Issues** tab in your
64
64
**Next:**[Interpret Your First Run](08b-interpret-your-run.md)
0 commit comments