Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Cerrado Apto para principiantes
  • ¿Algo no está bien?
#4,458 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
91/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github, markdown
Área
documentation

Línea de trabajo

Edita workshop/side-quest-26-01-forecast-costs.md, que según el issue contiene ambas descripciones obsoletas. Lee la Forecast Command Specification y la referencia de Cost Management enlazadas en el issue; después, actualiza la nota sobre el estado experimental y aclara que el límite de créditos de 24 horas suma las ejecuciones del mismo workflow en todo el repositorio. El trabajo estará terminado cuando ambas afirmaciones coincidan con el comportamiento documentado.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
JavaScript
Estrellas
53
Forks
35
Merge medio
13 h 50 min
PR fusionados (30 d)
14

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de githubnext/gh-aw-workshop

Todos los issues de githubnext/gh-aw-workshop

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.