[workshop-sync] side-quest-15-02-chaining-conditions.md: broken anchor link to workflow_dispatch trigger section
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, markdown
- Domain
- documentation
Research direction
The broken link is on line 72 of workshop/side-quest-15-02-chaining-conditions.md, in the 'Why chain with a branch check' section. Compare it with the same link in workshop/side-quest-13-04-token-optimization.md, which already uses the correct anchor. Change #dispatch-triggers-workflowdispatch to #dispatch-triggers-workflow_dispatch in the triggers reference URL. Done when the link on line 72 matches that form and the Dispatch Triggers section loads when followed.
Written by the indexing model from the issue text.
Description
Workshop file reviewed
workshop/side-quest-15-02-chaining-conditions.md (line 72)
Problem
The "Why chain with a branch check" section links to the triggers reference with an incorrect anchor:
...while still allowing a manual
workflow_dispatchto override from the Actions tab regardless of the current branch.
The anchor #dispatch-triggers-workflowdispatch does not match the live heading ID on https://github.github.com/gh-aw/reference/triggers/. I fetched the page and found the actual heading id is dispatch-triggers-workflow_dispatch (with an underscore between workflow and dispatch, matching the real GitHub Actions trigger name workflow_dispatch). The current link resolves to the top of the page instead of the Dispatch Triggers section.
Current correct syntax
The correct anchor is:
https://github.github.com/gh-aw/reference/triggers/#dispatch-triggers-workflow_dispatch
(Other workshop files, e.g. workshop/side-quest-13-04-token-optimization.md, already use this correct anchor form for the same link.)
Suggested fix
On line 72, replace:
https://github.github.com/gh-aw/reference/triggers/#dispatch-triggers-workflowdispatch
with:
https://github.github.com/gh-aw/reference/triggers/#dispatch-triggers-workflow_dispatch
Generated by 🔍 Workshop Sync Check · copilot · auto · 132.2 AIC · ⌖ 6.03 AIC · ⊞ 9.2K · ◷
- expires on Oct 11, 2026, 4:55 AM UTC
- Dominant language
- JavaScript
- Stars
- 52
- Forks
- 26
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 15
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
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/gh-aw-workshop#4496 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
githubnext/gh-aw-workshop#4495 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
githubnext/gh-aw-workshop#4494 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
githubnext/gh-aw-workshop#4491 ·
Maintainers usually reply within 1 day
-
[workshop-sync] workshop/06-install-gh-aw.md: inaccurate gh aw init output and stale version exampleOpendocumentation
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-workshop#4490 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
channels:add check:passed
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 9 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
swc-project/swc#12516 ·
Maintainers usually reply within 1 day
-
Opening Files on a demo drive logs you outPossibly taken @RChang06 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
omegaup/omegaup#10323 · 1 comment ·
Maintainers usually reply within 5 days
-
area/frontend good first issue kind/cooldown
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
kestra-io/kestra#20702 · 1 comment ·
Maintainers usually reply within 1 day