[guidelines] side-quest-07-01-compile-workflow.md: Checkpoint section hidden behind terminal-only journey wrapper
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, markdown
- Domain
- documentation
Research direction
Open workshop/side-quest-07-01-compile-workflow.md and inspect the journey markers around the Checkpoint section and closing Return to line. Narrow or remove the terminal-only wrapper so the required Checkpoint renders for every journey, then verify the page still preserves any genuinely terminal-specific content.
Written by the indexing model from the issue text.
Description
File reviewed
workshop/side-quest-07-01-compile-workflow.md
Violations
Checkpoint section conditionally hidden behind a journey marker on an all-journey page
Offending text:
<!-- journey: terminal --> ## :white_check_mark: Checkpoint - [ ] I know what `gh aw compile` checks before a workflow runs ... <!-- /journey -->(page-level annotation at top of file is
<!-- page-journey: all -->)
Suggested fix:
The whole ## :white_check_mark: Checkpoint section — plus the closing "Return to" line — is wrapped in a <!-- journey: terminal --> block, which will hide the required Checkpoint section from any learner journey other than terminal even though the page is declared page-journey: all. Per the guidelines, every non-dispatcher workshop step must end with a Checkpoint section, and journey markers should wrap path-specific callouts/next-links rather than the mandatory Checkpoint content. Remove the <!-- journey: terminal --> / <!-- /journey --> wrapper around the Checkpoint section (or narrow it to only the truly terminal-specific line) so the Checkpoint renders for all learners.
Generated by 📋 Guidelines Enforcer · copilot · auto · 115.2 AIC · ⌖ 6.37 AIC · ⊞ 9.1K · ◷
- expires on Sep 28, 2026, 4:04 AM UTC
- Dominant language
- JavaScript
- Stars
- 52
- Forks
- 26
- Avg merge
- 12h 54m
- 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
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
githubnext/gh-aw-workshop#4417 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
githubnext/gh-aw-workshop#4416 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 78/100
githubnext/gh-aw-workshop#4413 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/gh-aw-workshop#4410 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/gh-aw-workshop#4411 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
bug release:v5.56
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Jason-Vaughan/TangleClaw#2270 ·
Maintainers usually reply within 1 day
-
priority: medium tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
LeeAdcock/robocodeJs.com#411 ·
Maintainers usually reply within 1 day
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
mastra-ai/mastra#26635 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
chore good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pedrorchagas/blog-api#21 ·