From 65d2cc0696408698e7eb470b956a8dbabe2a84e6 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Sun, 15 Nov 2026 23:44:15 +0000 Subject: [PATCH] Extract Actions labeling exercise into side quest Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- workshop/04-github-actions-intro.md | 42 +----------- workshop/README.md | 1 + .../side-quest-04-01-label-workflow-parts.md | 67 +++++++++++++++++++ 3 files changed, 71 insertions(+), 39 deletions(-) create mode 100644 workshop/side-quest-04-01-label-workflow-parts.md diff --git a/workshop/04-github-actions-intro.md b/workshop/04-github-actions-intro.md index 0192639a..148df2bb 100644 --- a/workshop/04-github-actions-intro.md +++ b/workshop/04-github-actions-intro.md @@ -82,45 +82,10 @@ The agentic workflow file you'll author in this workshop is a `.md` file with th ## Label a sample workflow -The diagram below shows how the five key parts fit together in every workflow file. +Every workflow file is built from five parts: trigger, job, runner, step, and action. - - - - GitHub Actions workflow anatomy: trigger, job, runner, steps, and actions shown as nested layers - - -Before reading on, label each highlighted part of the workflow below with its type: -`trigger`, `job`, `runner`, `step`, or `action`. - -```yaml .github/workflows/hello-workflow.yml -on: [push] -jobs: - test: - runs-on: ubuntu-latest - steps: - - uses: actions/checkout@v4 - - run: echo "All checks passed" -``` - -Write a label beside each line: - -1. `on: [push]` -2. `test:` (the job name under `jobs:`) -3. `runs-on: ubuntu-latest` -4. `uses: actions/checkout@v4` -5. `run: echo "All checks passed"` - -
-Reveal the labels - -- `on: [push]` → **trigger** (when this workflow runs) -- `jobs: test:` → **job** (a group of steps that runs on one machine) -- `runs-on: ubuntu-latest` → **runner** (the machine type GitHub provisions) -- `uses: actions/checkout@v4` → **action** (a reusable step from the Actions marketplace) -- `run: echo "All checks passed"` → **step** (a shell command run directly on the runner) - -
+> [!TIP] +> **Optional Side Quest:** Want a quick labeling exercise with an anatomy diagram to lock in those five terms? Work through [Side Quest: Label the Parts of a Workflow](side-quest-04-01-label-workflow-parts.md), then come back here. ## Try it: Explore a real workflow @@ -138,7 +103,6 @@ Open a real workflow file and find the three core building blocks — no termina ## :white_check_mark: Checkpoint - [ ] You can identify `on`, `jobs`, and `steps` in a workflow file -- [ ] You labeled all five parts of the sample workflow above (trigger, job, runner, action, step) - [ ] You know workflows live in `.github/workflows/` - [ ] You explored a real workflow and found its trigger, a job name, and a step command - [ ] You can describe one way agentic workflows extend classic Actions (same trigger and runner; AI agent replaces fixed shell steps) diff --git a/workshop/README.md b/workshop/README.md index 0e7a5398..e448ea22 100644 --- a/workshop/README.md +++ b/workshop/README.md @@ -48,6 +48,7 @@ A hands-on workshop that takes you from zero to a fully automated, AI-powered wo - [Agentic Workflows for GitHub Actions Power Users](side-quest-05-01-actions-power-user.md) — one-page cheat sheet for what changes vs what stays the same in agentic workflows; branches from [Step 5](05-agentic-workflows-intro.md). - [Agentic Workflows Deep Dive](side-quest-05-02-aw-deep-dive.md) — classification exercises, example agent output, the two-file structure, and concept checks; branches from [Step 5](05-agentic-workflows-intro.md). +- [Label the Parts of a Workflow](side-quest-04-01-label-workflow-parts.md) — short labeling exercise with an anatomy diagram for trigger, job, runner, step, and action; branches from [Step 4](04-github-actions-intro.md). - [Terminal Basics](side-quest-01-01-terminal-basics.md) — optional primer that branches from [Step 1](01-prerequisites.md). - [Set Up Your Local Terminal](side-quest-02-01-local-terminal.md) — optional alternative for experienced terminal users who want to work on their own machine instead of in the recommended Codespace. - [Enterprise Setup Considerations](side-quest-enterprise-setup.md) — required reading for GHES users and useful for any managed enterprise environment; common return points include [Step 1](01-prerequisites.md), [Step 2](02a-setup-codespace.md), the [Local Terminal side quest](side-quest-02-01-local-terminal.md), and [Step 5](05-agentic-workflows-intro.md). diff --git a/workshop/side-quest-04-01-label-workflow-parts.md b/workshop/side-quest-04-01-label-workflow-parts.md new file mode 100644 index 00000000..fdcd57b0 --- /dev/null +++ b/workshop/side-quest-04-01-label-workflow-parts.md @@ -0,0 +1,67 @@ + + +# Side Quest: Label the Parts of a Workflow + +> _Optional: a two-minute labeling exercise that makes the five parts of every Actions workflow stick before you meet agentic workflows._ + +## :dart: What You'll Do + +You'll look at an anatomy diagram, then label each line of a small workflow as a trigger, job, runner, step, or action. + +## :clipboard: Before You Start + +- You read the Quick Refresher in [GitHub Actions in 5 Minutes](04-github-actions-intro.md). +- No tools or credentials needed. + +## Steps + +### Study the anatomy + +The diagram below shows how the five key parts fit together in every workflow file. + + + + + GitHub Actions workflow anatomy: trigger, job, runner, steps, and actions shown as nested layers + + +### Label each line + +Before reading on, label each highlighted part of the workflow below with its type: +`trigger`, `job`, `runner`, `step`, or `action`. + +```yaml .github/workflows/hello-workflow.yml +on: [push] +jobs: + test: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v4 + - run: echo "All checks passed" +``` + +Write a label beside each line: + +1. `on: [push]` +2. `test:` (the job name under `jobs:`) +3. `runs-on: ubuntu-latest` +4. `uses: actions/checkout@v4` +5. `run: echo "All checks passed"` + +
+Reveal the labels + +- `on: [push]` → **trigger** (when this workflow runs) +- `jobs: test:` → **job** (a group of steps that runs on one machine) +- `runs-on: ubuntu-latest` → **runner** (the machine type GitHub provisions) +- `uses: actions/checkout@v4` → **action** (a reusable step from the Actions marketplace) +- `run: echo "All checks passed"` → **step** (a shell command run directly on the runner) + +
+ +## :white_check_mark: Checkpoint + +- [ ] You labeled all five parts of the sample workflow (trigger, job, runner, action, step) +- [ ] You can explain the difference between a `run` step and a `uses` action + +**Return to the main adventure:** [GitHub Actions in 5 Minutes](04-github-actions-intro.md)