Skip to content

[workshop-diagrams] Add theme-aware explanatory diagram for token precedence - #3956

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
workshop-diagram/token-precedence-06-03b-31bf1c8716ca2cbd
Closed

github-actions[bot] wants to merge 1 commit into
mainfrom
workshop-diagram/token-precedence-06-03b-31bf1c8716ca2cbd

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Summary

Added a new theme-aware explanatory diagram to workshop/side-quest-06-03b-copilot-github-token.md, which had no existing images (this is a new concept, not a migration).

What changed

  • Workshop file: workshop/side-quest-06-03b-copilot-github-token.md — inserted one <picture> reference right after the intro paragraphs, before the "Shortest terminal path" section.
  • New SVGs:
    • workshop/images/06-03b-token-precedence-light.svg
    • workshop/images/06-03b-token-precedence-dark.svg

Why this diagram helps learners

This side quest explicitly warns (in prose, in two separate places) that copilot-requests: write silently overrides COPILOT_GITHUB_TOKEN — if the permission is present, the secret is ignored for inference. That's a decision learners must get right before wasting time debugging billing, but it was only explained in text. The diagram makes the precedence rule a single at-a-glance decision flow: workflow run → permission check → one of two outcomes (built-in inference vs. secret-based inference), with the "ignored, even if set" consequence called out directly on the built-in-inference branch.

QA performed

  • Ran node scripts/check-svg-visual-language.js — 0 violations.
  • Served the workshop folder locally and used Playwright to render the <picture> block:
    • colorScheme: "light" → currentSrc correctly resolves to ...-light.svg.
    • colorScheme: "dark" → currentSrc correctly resolves to ...-dark.svg.
  • Visually confirmed both variants are nonblank and all labels stay inside their boxes/chips at normal size.

Warning

Firewall blocked 7 domains

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

  • accounts.google.com
  • android.clients.google.com
  • clients2.google.com
  • registry.npmjs.org
  • update.googleapis.com
  • www.google.com
  • www.gstatic.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"
    - "registry.npmjs.org"
    - "update.googleapis.com"
    - "www.google.com"
    - "www.gstatic.com"

See Network Configuration for more information.

Generated by 🧠 Workshop Explanatory Diagram Generator · copilot · auto · 205.5 AIC · ⌖ 15.5 AIC · ⊞ 10.4K · ◷

  • expires on Sep 30, 2026, 2:49 AM UTC

…e quest

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown
Contributor Author

This pull request was automatically closed because it expired on 2026-09-30T02:49:33.009Z.

Closed by Workflow

@github-actions github-actions Bot closed this Sep 30, 2026
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.

0 participants