diff --git a/workshop/24-self-hosted-runners.md b/workshop/24-self-hosted-runners.md index 3289a4a1..fc1e1e0e 100644 --- a/workshop/24-self-hosted-runners.md +++ b/workshop/24-self-hosted-runners.md @@ -78,7 +78,7 @@ registration settings (Settings → Actions → Runners). > [!TIP] > Labels act as filters. A workflow job is dispatched to the first idle runner that satisfies all labels in the list. Adding `linux` alongside `self-hosted` ensures the job only lands on Linux runners when your fleet is mixed. -Running in an enterprise environment? See [Side Quest: Self-Hosted Runner Infrastructure Deep Dive](side-quest-24-01-runner-infrastructure.md) for guidance on ephemeral and JIT runners, proxy configuration, and [network](https://github.github.com/gh-aw/reference/network/) isolation for air-gapped environments. +Running in an enterprise environment? See [Side Quest: Self-Hosted Runner Infrastructure Deep Dive](side-quest-24-01-runner-infrastructure.md) for guidance on [ephemeral](https://github.github.com/gh-aw/reference/ephemerals/) and JIT runners, proxy configuration, and [network](https://github.github.com/gh-aw/reference/network/) isolation for air-gapped environments. ## :pencil2: Exercise: Compile and commit diff --git a/workshop/25-audit-and-observability.md b/workshop/25-audit-and-observability.md index 7c049d5d..734b8b3f 100644 --- a/workshop/25-audit-and-observability.md +++ b/workshop/25-audit-and-observability.md @@ -6,7 +6,7 @@ ## :dart: What You'll Do -Use `gh aw logs` and `gh aw audit` to review the built-in [artifacts](https://github.github.com/gh-aw/reference/artifacts/) that every agentic workflow run produces, understand [token usage](https://github.github.com/gh-aw/reference/cost-management/#monitoring-costs-with-gh-aw-logs), and debug unexpected behavior. By the end you know where to look when a run behaves unexpectedly or when a compliance review asks what the agent did. +Use `gh aw logs` and `gh aw audit` to review the built-in [artifacts](https://github.github.com/gh-aw/reference/artifacts/) that every agentic workflow run produces, understand [token usage](https://github.github.com/gh-aw/reference/cost-management/#monitoring-costs-with-gh-aw-logs), and debug unexpected behavior. By the end you know where to look when a run behaves unexpectedly or when a [compliance](https://github.github.com/gh-aw/reference/audit/) review asks what the agent did. ## :clipboard: Before You Start diff --git a/workshop/26-manage-costs-and-budgets.md b/workshop/26-manage-costs-and-budgets.md index e249d134..ed451901 100644 --- a/workshop/26-manage-costs-and-budgets.md +++ b/workshop/26-manage-costs-and-budgets.md @@ -75,7 +75,7 @@ A few techniques keep spend in check: - **Shorten the task brief** — fewer input tokens per run. - **Filter data before passing it to the agent** — smaller context lowers cost. -- **Cache results with persistent memory** — skip re-processing unchanged data. See [Make Your Workflow Remember Across Runs](20-persistent-memory.md). +- **Cache results with [persistent memory](https://github.github.com/gh-aw/reference/repo-memory/)** — skip re-processing unchanged data. See [Make Your Workflow Remember Across Runs](20-persistent-memory.md). - **Reduce run frequency** — fewer runs means fewer AIC. > [!TIP] diff --git a/workshop/27-evaluate-workflow-quality.md b/workshop/27-evaluate-workflow-quality.md index 4fe5ffdb..581c9c92 100644 --- a/workshop/27-evaluate-workflow-quality.md +++ b/workshop/27-evaluate-workflow-quality.md @@ -30,7 +30,7 @@ You'll add an `evals:` block to your workflow, define binary quality questions, ### Add an `evals:` block -Open `.github/workflows/daily-status.md` and add binary questions to frontmatter. +Open `.github/workflows/daily-status.md` and add binary questions to [frontmatter](https://github.github.com/gh-aw/reference/frontmatter/). ```markdown .github/workflows/daily-status.md --- diff --git a/workshop/28-orchestrate-workflows.md b/workshop/28-orchestrate-workflows.md index 48c858a3..14db6719 100644 --- a/workshop/28-orchestrate-workflows.md +++ b/workshop/28-orchestrate-workflows.md @@ -107,9 +107,9 @@ gh aw compile repo-orchestrator -### Review the `dispatch-workflow` safe-output +### Review the `dispatch-workflow` [safe-output](https://github.github.com/gh-aw/reference/safe-outputs/#workflow-dispatch-dispatch-workflow) -After the skill or your manual edit creates the file, confirm the frontmatter contains: +After the skill or your manual edit creates the file, confirm the [frontmatter](https://github.github.com/gh-aw/reference/frontmatter/) contains: ```markdown .github/workflows/repo-orchestrator.md safe-outputs: diff --git a/workshop/side-quest-01-02-environment-reference.md b/workshop/side-quest-01-02-environment-reference.md index d21c7b0e..21e49fbd 100644 --- a/workshop/side-quest-01-02-environment-reference.md +++ b/workshop/side-quest-01-02-environment-reference.md @@ -100,7 +100,7 @@ You use `gh` for GitHub-specific terminal tasks like authentication checks, repo Conceptual screenshot of the gh-aw CLI extension showing compile commands for an agentic workflow -You use `gh aw` to compile agentic workflow files. +You use `gh aw` to compile [agentic workflow](https://github.github.com/gh-aw/introduction/overview/#what-is-an-agentic-workflow) files. #### GitHub Copilot CLI