Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[workshop-sync] side-quest-26-01-forecast-costs.md: `gh aw forecast` experimental note is outdated; `max-daily-ai-credits` scope description is

Open Beginner friendly
  • Is something wrong?
#4,458 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
91/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github, markdown
Domain
documentation

Research direction

Edit workshop/side-quest-26-01-forecast-costs.md, which the issue identifies as containing both outdated descriptions. Read the Forecast Command Specification and Cost Management reference linked in the issue, then update the experimental-status note and clarify that the 24-hour credit cap sums runs of the same workflow across the repository. Done when both statements match the documented behavior.

Written by the indexing model from the issue text.

Description

documentation

Workshop file reviewed

workshop/side-quest-26-01-forecast-costs.md

Problem 1 — stale "experimental" callout

Near the top of the file:

> [!NOTE]
> gh aw forecast is currently experimental. Its flags and output format may change in future releases.

This is no longer accurate. The gh-aw Forecast Command Specification states:

"This is a Draft specification. The gh aw forecast command is a stable, generally available command; forecasts it produces are probabilistic estimates and may be inaccurate."

The spec's Change Log for Version 1.0.0 explicitly records:

  • "Promoted the gh aw forecast command out of experimental status"
  • "Removed the experimental-status stderr warning and [EXPERIMENTAL] command labels"
  • "Replaced the experimental warning ... with an accuracy-disclosure note: 'All forecasts are estimates derived from historical samples and may be inaccurate.'"

The current installed gh aw CLI help snapshot (gh aw forecast --help) also no longer shows any [EXPERIMENTAL] label, confirming this change is already live.

Current correct behaviour

gh aw forecast is stable/generally available. The workshop should either drop the "currently experimental" callout or replace it with the current accuracy-disclosure framing ("forecasts are estimates derived from historical samples and may be inaccurate").

Suggested fix

Replace the [!NOTE] block with something like:

> [!NOTE]
> gh aw forecast is a stable command, but its output is a statistical estimate — treat P10/P50/P90 figures as probabilistic projections, not guarantees.

Problem 2 — incorrect scope description for max-daily-ai-credits

In the "Translate the P90 into max-daily-ai-credits" section:

"The max-daily-ai-credits field caps how many AIC a workflow can consume across the last 24 hours for the triggering user."

This is incorrect. Per the gh-aw Cost Management reference:

"Use max-daily-ai-credits to set a 24-hour AI Credits cap for one workflow. The guardrail sums runs from the past 24 hours of the same workflow across the repository, regardless of who triggered them."

So the cap applies per-workflow, repository-wide — not scoped to an individual triggering user.

Current correct syntax/behaviour

max-daily-ai-credits sums AIC usage for a given workflow across all triggers in the repository over the trailing 24-hour window, not just the user who triggered the current run.

Suggested fix

Update the sentence to:

"The max-daily-ai-credits field caps how many AIC a workflow can consume across the last 24 hours, summed across all runs of that workflow in the repository regardless of who triggered them."

Generated by 🔍 Workshop Sync Check · copilot · auto · 140.7 AIC · ⌖ 9.31 AIC · ⊞ 9.2K · ◷

  • expires on Oct 12, 2026, 10:47 AM UTC
Dominant language
JavaScript
Stars
52
Forks
26
Avg merge
12h 54m
Merged PRs (30d)
17

Getting set up

Open in Codespaces

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from githubnext/gh-aw-workshop

All issues in githubnext/gh-aw-workshop

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.