[workshop-sync] workshop/side-quest-11-02-yaml-frontmatter.md: `emoji: :bar_chart:` is invalid YAML
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- yaml
- Domain
- documentation
Research direction
Open workshop/side-quest-11-02-yaml-frontmatter.md and inspect lines 78 and 90. Confirm the emoji syntax against the linked gh-aw frontmatter reference, then update both examples to use the single emoji character. Done means both examples show valid YAML; the issue identifies the exact file and change.
Written by the indexing model from the issue text.
Description
Workshop file reviewed
workshop/side-quest-11-02-yaml-frontmatter.md
Problem
Lines 78 and 90 (both the ❌ and ✅ examples) use:
emoji: :bar_chart:
An unquoted value starting with : and ending with : is a YAML parse error (verified with a YAML parser: "mapping values are not allowed here"). The page is about avoiding YAML errors, so the "correct" example is itself broken.
Current correct syntax
emoji: takes a single emoji character, e.g. emoji: 📊 (see gh-aw frontmatter reference: https://github.github.com/gh-aw/reference/frontmatter/).
Suggested fix
Replace :bar_chart: with 📊 on lines 78 and 90.
Reviewed in the same run with no issues: workshop/side-quest-11-01b-workflow-structure.md, workshop/side-quest-11-03-better-prompts.md. gh-aw release: v1.0.1.
Generated by 🔍 Workshop Sync Check · copilot · auto · ~52 AIC · ⌖ ~1 AIC · ⊞ 4.7K · ◷
- expires on Nov 6, 2026, 12:04 PM UTC
- Dominant language
- JavaScript
- Stars
- 58
- Forks
- 40
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 8
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
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
githubnext/gh-aw-workshop#5437 ·
Maintainers usually reply within 3 days
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
githubnext/gh-aw-workshop#5436 ·
Maintainers usually reply within 3 days
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
githubnext/gh-aw-workshop#5434 ·
Maintainers usually reply within 3 days
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
githubnext/gh-aw-workshop#5433 ·
Maintainers usually reply within 3 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
githubnext/gh-aw-workshop#5427 ·
Maintainers usually reply within 3 days
All issues in githubnext/gh-aw-workshop
Similar issues
-
stringify escapes leading digits in pseudo-class arguments (:nth-child(1) becomes :nth-child(\31 ))Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
digitalbazaar/forge#1170 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-form#664 ·
-
bug web-ui
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
jenkinsci/jenkins#27705 · 3 comments ·
Maintainers usually reply within 1 day