[ordering-review] workshop order graph: 1 ordering issue, 3 cycles reviewed as benign

Abierto Apto para principiantes
  • ¿Algo no está bien?
#5,635 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
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
66/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github
Área
documentation

Línea de trabajo

El problema está en workshop/side-quest-01-02-environment-reference.md. Lee el texto de "Before You Start" y la sección "Verify your tools are ready", luego revisa el enlace a la rama en README.md y la configuración de Codespace en 02a-setup-codespace.md. Está terminado cuando el paso de verificación queda condicionado a completar la configuración (o la side quest de terminal local), o se mueve a 02a, y el texto de "Before You Start" lo indica. Ejecuta npx --yes markdownlint-cli2 "**/*.md" para confirmar que la edición está limpia.

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

Descripción

Graph health summary

The generated report covered 97 pages, 338 constraints, 57 potential findings, 3 cycles, 3 feedback loops and 3 weird cycles. I checked the cited pages and confirmed one real ordering problem. The cycles and the 50 gh_authenticated "missing_prerequisite_link" findings are false positives (details below).

Mermaid graph (reduced to the pages involved in verified or cited anomalies; the full graph is in the generated report)
graph TD
  n01["01 Prerequisites"] --> n02a["02a Set Up a Codespace"]
  n01 -. branches .-> sq0102["01-SQ02 Environment Reference"]
  n01 -. branches .-> sq0201["02-SQ01 Local Terminal"]
  sq0201 -. fallback link .-> n02a
  n02a --> n05["05 What Are Agentic Workflows?"]
  n05 --> n05b["05b How Agentic Workflows Stay Safe"]
  n05b -. prerequisite .-> n05
  n05b --> n06["06 Install gh-aw"]
  n06 --> n07["07 Your First Workflow"]
  n07 --> n07d["07d Confirm Model Access"]
  n07 -. error recovery link .-> n07d
  n07d -. return link .-> n07
  n07d --> n08["08 Run Your Workflow"]
  n16["16 Connect Data Source"] -. links to .-> sq0102
Ordering constraints (key subset)
  • 01 -> 02a (or 02-SQ01 local path) -> 06 (install gh-aw) -> 07 -> 07d -> 08.
  • Every gh/gh aw command requires an opened Codespace or local terminal (environment_ready), which 02a or 02-SQ01 provides.
  • gh aw commands require the extension installed in 06.
  • 05b requires 05; 07d requires 07 (normal flow) or can precede it (model-access error recovery).
Confirmed cycles, feedback loops, weird cycles

All three are intentional and benign:

  • 07 <-> 07d: 07d documents two entry points (error recovery from 07, or the normal next step). Deliberate.
  • 05 <-> 05b: 05 only mentions 05b in inline prose ("You will explore security in..."). Only 05b lists 05 as a prerequisite, so this is not a real dependency loop.
  • 02a <-> 02-SQ01: the local-terminal side quest links back to 02a as a fallback ("switch to Set Up a Codespace"). This is an optional escape hatch, not a prerequisite.

The missing_prerequisite_link findings for gh_authenticated (about 50 pages) are heuristic noise: authentication is provided by the Codespace/gh setup in 02a/06 and is not a missing link per page.

Verified ordering problem

workshop/side-quest-01-02-environment-reference.md

  • Quoted instruction that appears too early:

    :white_check_mark: Verify your tools are ready

    Open a terminal in your Codespace and run: gh --version, git --version, gh auth status

    (also the gh aw compile note: "the gh aw compile command still runs locally in your Codespace")

  • Missing earlier step: this side quest branches from 01-prerequisites.md (see README.md: "branches from Step 1"), and its Before You Start says "you can read it any time". But the Codespace (02a-setup-codespace.md) or local terminal (side-quest-02-01-local-terminal.md) does not exist yet at that point, and it also claims gh is "Pre-installed in the Codespace".

  • Why it confuses learners: a learner who follows the side quest from Step 1 is told to open a terminal "in your Codespace" and run verification commands before any Codespace has been created, and the page says no terminal is required to read it.

  • Suggested fix: in side-quest-01-02-environment-reference.md, either (a) change the "Verify your tools are ready" section to start with a conditional: "Once you have completed Set Up a Codespace (link unavailable: invalid HTTPS URL) (or the local terminal side quest), open a terminal and run:" or (b) move the verification block to 02a-setup-codespace.md, where the environment is first available. Also update the Before You Start text to say the verification block applies only after setup.

Notes

This issue is ready for an agent to resolve. Run npx --yes markdownlint-cli2 "**/*.md" after the edit, and assess golden-ticket branch impact (likely none: the page is a reference side quest).

Generated by 🧭 Workshop Order Review · copilot · auto · ~24 AIC · ⌖ ~1 AIC · ⊞ 4.8K · ◷

  • expires on Nov 13, 2026, 12:01 PM UTC
Lenguaje dominante
JavaScript
Estrellas
62
Forks
43
Merge medio
1 d 5 h
PR fusionados (30 d)
9

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.