[workshop-sync] workshop/side-quest-11-02-yaml-frontmatter.md: `emoji: :bar_chart:` is invalid YAML
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, yaml
- Domain
- documentation
Research direction
Read workshop/side-quest-11-02-yaml-frontmatter.md around lines 78 and 90, then check the three related workshop files named in the issue for the same :bar_chart: examples. Replace the invalid YAML values consistently with a literal emoji or a quoted value. Done when each example parses as intended and the exercises remain consistent with the corrected examples.
Written by the indexing model from the issue text.
Description
Workshop file reviewed
workshop/side-quest-11-02-yaml-frontmatter.md (lines ~78 and ~90)
Problem
Both "Forgetting the closing ---" examples use:
emoji: :bar_chart:
An unquoted plain scalar of :bar_chart: fails YAML parsing ("mapping values are not allowed here"). The page teaches YAML errors, so its "correct" example is itself broken. Also, the gh-aw frontmatter reference (emoji:) describes a single emoji character, and the repo's own workflows use literal emoji (e.g. emoji: 🔬).
Suggested fix
Use a literal emoji (emoji: 📊) or quote the value (emoji: ":bar_chart:") in both examples.
The same pattern appears in side-quest-11-01-frontmatter-deep-dive.md, side-quest-11-01b-workflow-structure.md and side-quest-11-04-annotated-workflow.md (line 35; its exercises also say to change :bar_chart: to :mag:), so fix those together.
Note: gh-aw release v0.92.0 was the latest at review time. Files side-quest-11-03-better-prompts.md and side-quest-11-04 otherwise had no command drift (gh aw list, gh aw compile --validate exist in CLI help).
Generated by 🔍 Workshop Sync Check · copilot · auto · 22.5 AIC · ⌖ 0.541 AIC · ⊞ 9.2K · ◷
- expires on Oct 23, 2026, 4:50 AM UTC
- Dominant language
- JavaScript
- Stars
- 55
- Forks
- 36
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 17
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from githubnext/gh-aw-workshop
-
[workshop-sim] Improve: Strengthen practice and checkpoints in Step 05 (What Are Agentic Workflows?)Openfeedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
githubnext/gh-aw-workshop#4972 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
githubnext/gh-aw-workshop#4971 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
githubnext/gh-aw-workshop#4969 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 Half a day Newbie friendliness 85/100
githubnext/gh-aw-workshop#4966 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
githubnext/gh-aw-workshop#4964 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
Clinic sharing: fast sync refusal message suggests Delete Data, which only developer builds haveOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
avniproject/avni-client#2228 ·
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-webui/open-webui#33196 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fable-compiler/Fable#5157 ·
Maintainers usually reply within 1 day
-
New tool: PaperBananaPossibly taken @github-actions claimed this today. Opensubmission triage
Difficulty 1/5 Under an hour Newbie friendliness 75/100
kausalflow/tools#243 · 1 comment ·
Maintainers usually reply within 1 day
-
area: apple-music area: build-release bug effort: small priority: high
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ChristianTabor/Argon#32 ·
Maintainers usually reply within 1 day