[workshop-sync] 26-manage-costs-and-budgets.md: stale `#forecast-experimental` anchor link
Maintainers usually reply within 1 day
@sadhana-s-codez is already working on this.
Since Oct 13, 2026.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 95/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, markdown
- Domain
- documentation
Research direction
Open workshop/26-manage-costs-and-budgets.md and find the “Project costs with gh aw forecast” heading. Change its link fragment from #forecast-experimental to #forecast; the work is done when the heading links to the existing docs anchor.
Written by the indexing model from the issue text.
Description
Workshop file reviewed
workshop/26-manage-costs-and-budgets.md
Problem
The "Project costs with gh aw forecast" section links to a docs anchor that no longer exists:
### Project costs with [gh aw forecast](https://github.github.com/gh-aw/setup/cli/#forecast-experimental)
On the live docs page (https://github.github.com/gh-aw/setup/cli/), the heading anchor for this section is simply id="forecast" — there is no forecast-experimental anchor, and the page text no longer labels forecast as experimental; the gh aw --help snapshot (gh_aw_help) also lists forecast under "Analysis Commands" without an "Experimental" marker (unlike edit, which is still explicitly marked "Experimental: edit workflow frontmatter and recompile"). This means the link in the workshop currently points to a broken in-page anchor.
Current correct syntax
Update the link to use the real anchor:
### Project costs with [gh aw forecast](https://github.github.com/gh-aw/setup/cli/#forecast)
No other "experimental" framing needs to be added around gh aw forecast elsewhere in the file — the rest of the section already treats it as a normal, supported command.
Suggested fix
In workshop/26-manage-costs-and-budgets.md, change the anchor in the gh aw forecast heading link from #forecast-experimental to #forecast.
Generated by 🔍 Workshop Sync Check · copilot · auto · 131.4 AIC · ⌖ 7.59 AIC · ⊞ 9.2K · ◷
- expires on Oct 14, 2026, 8:58 AM UTC
- Dominant language
- JavaScript
- Stars
- 53
- Forks
- 35
- Avg merge
- 13h 50m
- Merged PRs (30d)
- 14
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#4571 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/gh-aw-workshop#4569 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/gh-aw-workshop#4568 ·
Maintainers usually reply within 1 day
-
accessibility bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
githubnext/gh-aw-workshop#4555 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
githubnext/gh-aw-workshop#4548 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
internal os specific
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
frostney/GocciaScript#1688 ·
Maintainers usually reply within 1 day
-
🐞 bug pending triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
CircuitVerse/CircuitVerse#8031 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 8 days
-
docs(stream-protocol): document messageMetatadata on start/finish and the message-metadata chunkPossibly taken A pull request linked to this issue is open or already merged. Openfactory-active task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 7 days