Skip to content

[workshop-diagrams] Add explanatory SVG diagram for workflow_dispatch trigger#1180

Merged
pelikhan merged 1 commit into
mainfrom
add-workflow-dispatch-diagram-4769a538a9c3eec6
Jul 15, 2026
Merged

[workshop-diagrams] Add explanatory SVG diagram for workflow_dispatch trigger#1180
pelikhan merged 1 commit into
mainfrom
add-workflow-dispatch-diagram-4769a538a9c3eec6

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Summary

This PR adds a conceptual explanatory diagram to the terminal path for Step 7a of the workshop.

Workshop file changed

workshop/07a-your-first-workflow-terminal.md

Concept illustrated

workflow_dispatch: How Manual Triggers Work — the diagram shows the four-stage flow:

  1. Author — write hello-agent.md with on: workflow_dispatch frontmatter
  2. Compilegh aw compile generates hello-agent.lock.yml
  3. Actions Tab — after pushing, the workflow appears in the GitHub Actions sidebar with a "Run workflow" button
  4. Agent Runs — clicking the button triggers the Copilot agent

A lower panel contrasts workflow_dispatch with other trigger types (push, schedule, pull_request) to help learners understand why manual triggering is the right choice while learning.

SVG file added

workshop/images/07a-workflow-dispatch-trigger.svg

Why it helps learners

The workflow_dispatch keyword is new to most learners. Before this diagram, the file only had a bullet point saying "workflow_dispatch means you can run it manually while testing" — the visual makes the full authoring → compile → push → trigger cycle immediately clear, and the trigger comparison panel helps learners understand when they would choose each trigger type in future workflows.

QA

  • Playwright render check passed: all text stays within its respective boxes and containers at normal browser zoom
  • Markdownlint reports 0 errors on the modified file

Warning

Firewall blocked 5 domains

The following domains were blocked by the firewall during workflow execution:

  • accounts.google.com
  • android.clients.google.com
  • clients2.google.com
  • safebrowsingohttpgateway.googleapis.com
  • www.google.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "accounts.google.com"
    - "android.clients.google.com"
    - "clients2.google.com"
    - "safebrowsingohttpgateway.googleapis.com"
    - "www.google.com"

See Network Configuration for more information.

Generated by 🧠 Workshop Explanatory Diagram Generator · 107.1 AIC · ⌖ 9.7 AIC · ⊞ 5.9K ·

  • expires on Jul 16, 2026, 5:36 AM UTC

Adds 07a-workflow-dispatch-trigger.svg illustrating how the
workflow_dispatch trigger works: from authoring the .md file,
compiling to a .lock.yml, pushing to GitHub, and manually
clicking 'Run workflow' in the Actions tab.

Inserts the image reference in workshop/07a-your-first-workflow-terminal.md
next to the explanation of the workflow_dispatch frontmatter field.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@pelikhan pelikhan marked this pull request as ready for review July 15, 2026 05:57
@pelikhan pelikhan merged commit 429a6c6 into main Jul 15, 2026
@pelikhan pelikhan deleted the add-workflow-dispatch-diagram-4769a538a9c3eec6 branch July 15, 2026 05:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant