Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 3 additions & 39 deletions workshop/04-github-actions-intro.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<picture>
<source media="(prefers-color-scheme: dark)" srcset="images/04-actions-anatomy-dark.svg">
<source media="(prefers-color-scheme: light)" srcset="images/04-actions-anatomy-light.svg">
<img alt="GitHub Actions workflow anatomy: trigger, job, runner, steps, and actions shown as nested layers" src="images/04-actions-anatomy-light.svg">
</picture>

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"`

<details>
<summary>Reveal the labels</summary>

- `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)

</details>
> [!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

Expand All @@ -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)
Expand Down
1 change: 1 addition & 0 deletions workshop/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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).
Expand Down
67 changes: 67 additions & 0 deletions workshop/side-quest-04-01-label-workflow-parts.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,67 @@
<!-- page-journey: all -->
<!-- page-adventure: side-quest -->
# 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.

<picture>
<source media="(prefers-color-scheme: dark)" srcset="images/04-actions-anatomy-dark.svg">
<source media="(prefers-color-scheme: light)" srcset="images/04-actions-anatomy-light.svg">
<img alt="GitHub Actions workflow anatomy: trigger, job, runner, steps, and actions shown as nested layers" src="images/04-actions-anatomy-light.svg">
</picture>

### 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"`

<details>
<summary>Reveal the labels</summary>

- `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)

</details>

## :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)