[workshop-sync] workshop/side-quest-13-04-token-optimization.md: broken AI credits guardrail doc anchors
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, markdown
- Domain
- documentation
Research direction
Open workshop/side-quest-13-04-token-optimization.md and inspect the two links on lines 111–112. Confirm the target section names in reference/cost-management.md, then update the URLs to point to the listed anchors. Done when both links resolve to the AI credits guardrail sections.
Written by the indexing model from the issue text.
Description
Workshop file reviewed
workshop/side-quest-13-04-token-optimization.md (reviewed with side-quest-15-01-expressions-and-contexts.md and side-quest-15-02-chaining-conditions.md, which had no findings). gh-aw release: v0.93.0.
Problem
Lines 111–112 link to anchors that no longer exist on the triggers reference page:
[max-ai-credits](https://github.github.com/gh-aw/reference/triggers/#ai-credits-guardrail-max-ai-credits)
[max-daily-ai-credits](https://github.github.com/gh-aw/reference/triggers/#daily-per-workflow-ai-credits-guardrail-max-daily-ai-credits)
The current docs/src/content/docs/reference/triggers.md in github/gh-aw has no AI Credits guardrail sections. These guardrails are documented in reference/cost-management.md under "Cap AI Credits per Run" and "Cap Daily AI Credits per Workflow".
Suggested fix
max-ai-credits→https://github.github.com/gh-aw/reference/cost-management/#cap-ai-credits-per-runmax-daily-ai-credits→https://github.github.com/gh-aw/reference/cost-management/#cap-daily-ai-credits-per-workflow
Note: the CLI flags used in the file (gh aw logs --count, gh aw audit --parse) match the live gh aw help.
Generated by 🔍 Workshop Sync Check · copilot · auto · 24.8 AIC · ⌖ 0.55 AIC · ⊞ 9.2K · ◷
- expires on Oct 24, 2026, 1:48 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
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#4897 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
githubnext/gh-aw-workshop#4896 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
githubnext/gh-aw-workshop#4878 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
githubnext/gh-aw-workshop#4879 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
githubnext/gh-aw-workshop#4877 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rescript-lang/rescript#8996 ·
Maintainers usually reply within 1 day
-
check:passed logos:add
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
fossasia/visdom-dev#69 ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
-
建议写成 1949-Open
Difficulty 1/5 Under an hour Newbie friendliness 62/100
DeanChensj/jiangshan-map#133 ·
Maintainers usually reply within 1 day