Skip to content

[workshop-diagrams] Add theme-aware explanatory diagram for run error checks - #2588

Merged
pelikhan merged 1 commit into
mainfrom
add-08b-error-checks-diagram-e9995a2f8b3f2545
Aug 11, 2026
Merged

[workshop-diagrams] Add theme-aware explanatory diagram for run error checks#2588
pelikhan merged 1 commit into
mainfrom
add-08b-error-checks-diagram-e9995a2f8b3f2545

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

What changed

Workshop file: workshop/08b-interpret-your-run.md

Change type: New concept diagram (not a migration — no existing diagram covered this topic)

New SVG files:

  • workshop/images/08b-error-checks-light.svg
  • workshop/images/08b-error-checks-dark.svg

Why this diagram helps learners

The "Check common error patterns first" section previously described three diagnostic checks only as prose bullet points. Learners had to mentally map the decision logic themselves. The new diagram renders this as a top-to-bottom decision flow:

  1. Does the workflow appear in Actions? → If No: commit to main and compile
  2. Does the log show useful tool calls? → If No: refine the brief
  3. Did something change in GitHub? → If No: check issue and permissions; If Yes: run looks good

This lets learners scan the decision tree at a glance and immediately locate which fix applies to their situation, reducing back-and-forth between the prose and the actual Actions tab.

QA

  • check-svg-visual-language.js — 0 violations on both files
  • markdownlint-cli2 — 0 issues
  • ✅ Playwright light: currentSrc ends with -light.svg, dimensions 1200×560, nonblank
  • ✅ Playwright dark: currentSrc ends with -dark.svg, nonblank (62 KB screenshot)

Warning

Firewall blocked 6 domains

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

  • accounts.google.com
  • awmgmcpg
  • clients2.google.com
  • safebrowsingohttpgateway.googleapis.com
  • storage.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"
    - "awmgmcpg"
    - "clients2.google.com"
    - "safebrowsingohttpgateway.googleapis.com"
    - "storage.googleapis.com"
    - "www.google.com"

See Network Configuration for more information.

Generated by 🧠 Workshop Explanatory Diagram Generator · 109.9 AIC · ⌖ 9.82 AIC · ⊞ 6.8K ·

  • expires on Aug 12, 2026, 5:07 AM UTC

Add a new light/dark SVG pair that visualises the three quick checks
learners should perform when a run does not look right:

1. Does the workflow appear in Actions?
2. Does the log show useful tool calls?
3. Did something change in GitHub?

Each check has a Yes path (continue to the next check / reach the
'Run looks good' terminal) and a No path pointing to a concrete fix.

Files added:
  workshop/images/08b-error-checks-light.svg
  workshop/images/08b-error-checks-dark.svg

Markdown change:
  workshop/08b-interpret-your-run.md — inserted a <picture> block with
  a two-sentence introduction immediately before the prose checklist in
  the 'Check common error patterns first' section.

SVGs pass check-svg-visual-language.js and markdownlint.
Playwright confirms light currentSrc ends with -light.svg and dark
currentSrc ends with -dark.svg; both images are 1200×560 and nonblank.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@pelikhan
pelikhan marked this pull request as ready for review August 11, 2026 15:33
@pelikhan
pelikhan merged commit e89e28c into main Aug 11, 2026
24 checks passed
@pelikhan
pelikhan deleted the add-08b-error-checks-diagram-e9995a2f8b3f2545 branch August 11, 2026 23:02

@albertoblue87-netizen albertoblue87-netizen left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Listo

@albertoblue87-netizen albertoblue87-netizen left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Listo

@albertoblue87-netizen albertoblue87-netizen left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Listo

@albertoblue87-netizen albertoblue87-netizen left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Listo

@albertoblue87-netizen albertoblue87-netizen left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Listo

@albertoblue87-netizen albertoblue87-netizen left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Listo

@albertoblue87-netizen albertoblue87-netizen left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Listo

@albertoblue87-netizen albertoblue87-netizen left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Listo

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.

2 participants