From 7dbd82bc34f0bb74ffce93318b5c23b205641d70 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Sat, 19 Sep 2026 02:39:10 +0000 Subject: [PATCH] Add theme-aware explanatory diagram for standard vs. agentic workflow classification Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .../side-quest-05-02-classify-flow-dark.svg | 72 +++++++++++++++++++ .../side-quest-05-02-classify-flow-light.svg | 72 +++++++++++++++++++ workshop/side-quest-05-02-aw-deep-dive.md | 8 +++ 3 files changed, 152 insertions(+) create mode 100644 workshop/images/side-quest-05-02-classify-flow-dark.svg create mode 100644 workshop/images/side-quest-05-02-classify-flow-light.svg diff --git a/workshop/images/side-quest-05-02-classify-flow-dark.svg b/workshop/images/side-quest-05-02-classify-flow-dark.svg new file mode 100644 index 00000000..0b065d23 --- /dev/null +++ b/workshop/images/side-quest-05-02-classify-flow-dark.svg @@ -0,0 +1,72 @@ + + + + + Standard vs. agentic: same trigger, different path + Read left to right: one trigger, two possible kinds of steps. + + + + Trigger + on: pull_request + + + + + + + + + 1. Standard workflow — fixed steps + Same result every run. No judgment required. + + + Run tests + npm test + + + + + + Fail on non-zero + exit code check + + + + + + Upload coverage + same output every run + + + + + + 2. Agentic workflow — judgment calls + Output differs each run based on live context. + + + Read issues + live repo context + + + + + + Judge & group + agent decision + + + + + + Post summary + varies each run + + + Key signal: fixed steps every run mean standard; judgment on live context that changes the output means agentic. + diff --git a/workshop/images/side-quest-05-02-classify-flow-light.svg b/workshop/images/side-quest-05-02-classify-flow-light.svg new file mode 100644 index 00000000..edeaba1c --- /dev/null +++ b/workshop/images/side-quest-05-02-classify-flow-light.svg @@ -0,0 +1,72 @@ + + + + + Standard vs. agentic: same trigger, different path + Read left to right: one trigger, two possible kinds of steps. + + + + Trigger + on: pull_request + + + + + + + + + 1. Standard workflow — fixed steps + Same result every run. No judgment required. + + + Run tests + npm test + + + + + + Fail on non-zero + exit code check + + + + + + Upload coverage + same output every run + + + + + + 2. Agentic workflow — judgment calls + Output differs each run based on live context. + + + Read issues + live repo context + + + + + + Judge & group + agent decision + + + + + + Post summary + varies each run + + + Key signal: fixed steps every run mean standard; judgment on live context that changes the output means agentic. + diff --git a/workshop/side-quest-05-02-aw-deep-dive.md b/workshop/side-quest-05-02-aw-deep-dive.md index bec7200c..1bfa3acb 100644 --- a/workshop/side-quest-05-02-aw-deep-dive.md +++ b/workshop/side-quest-05-02-aw-deep-dive.md @@ -14,6 +14,14 @@ A standard Actions workflow runs the same fixed steps every time — no judgment **Key signal:** if the output could be different each run because the agent is reading context and making decisions, it's agentic. +The same trigger can lead down either path, as shown below. + + + + + Diagram comparing a standard workflow that always runs the same fixed steps with an agentic workflow where the agent reads context and makes judgment calls, producing output that varies each run. + + ## Classify Task A **Task:** Run unit tests on every pull request, fail if any test exits non-zero, and upload coverage.