Skip to content
Closed
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
72 changes: 72 additions & 0 deletions workshop/images/side-quest-05-02-classify-flow-dark.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
72 changes: 72 additions & 0 deletions workshop/images/side-quest-05-02-classify-flow-light.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
8 changes: 8 additions & 0 deletions workshop/side-quest-05-02-aw-deep-dive.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<picture>
<source media="(prefers-color-scheme: dark)" srcset="images/side-quest-05-02-classify-flow-dark.svg">
<source media="(prefers-color-scheme: light)" srcset="images/side-quest-05-02-classify-flow-light.svg">
<img alt="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." src="images/side-quest-05-02-classify-flow-light.svg">
</picture>

## Classify Task A

**Task:** Run unit tests on every pull request, fail if any test exits non-zero, and upload coverage.
Expand Down