[ordering-review] workshop order graph: 1 confirmed ordering problem, 3 benign cycles

Abierto Apto para principiantes
#5,959 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
68/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions

Línea de trabajo

Empieza con workshop/05-agentic-workflows-intro.md alrededor de la línea 53, donde la Actividad 1 pide al alumno que abra un archivo .lock.yml que todavía no existe, y revisa workshop/07-your-first-workflow.md para ver dónde ocurre la primera compilación. Hecho significa que el alumno ya no puede encontrarse con un archivo inexistente en el paso 05, ya sea apuntando a un archivo lock de ejemplo o moviendo la actividad después del paso 07, con el checkpoint reformulado en consecuencia.

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

Descripción

Graph health summary

Reviewed 98 workshop pages (3 dispatcher/informational), 346 edges and 59 heuristic findings. After checking the cited files, 1 real ordering problem is confirmed. The 3 reported cycles are benign navigation loops. Most of the 50 missing_prerequisite_link findings are false positives: they come from concept or reference pages that mention gh aw compile without asking the learner to run it.

Mermaid graph (core spine, simplified)

The full 98-node graph is in the generated order-review-report.md artifact.

graph TD
  W00[00 welcome] --> P01[01 prerequisites]
  P01 --> S02a[02a setup codespace]
  P01 -.alt.-> SQ0201[02-SQ01 local terminal]
  SQ0201 -.fallback.-> S02a
  S02a --> S04[04 Actions intro]
  SQ0201 --> S04
  S04 --> S05[05 agentic workflows intro]
  S05 --> S05b[05b security]
  S05b --> S05c[05c practice]
  S05c --> S06[06 install gh-aw]
  S06 --> S07[07 first workflow]
  S07 --> S07d[07d confirm model access]
  S07d -.return on error.-> S07
  S07 --> S08[08 run workflow]
  S08 --> S08b[08b interpret run]
  S08b --> S09[09 agentic editing]

Ordering constraints (key ones)

  • 01 prerequisites → 02a setup codespace (or 02-SQ01 local terminal) → 04 → 05 → 05b → 05c → 06 install gh-aw → 07 → 08 → 08b → 09
  • 02a or 02-SQ01 must provide environment_ready, gh_installed and gh_authenticated before any gh or gh aw command.
  • 06 must provide gh-aw before 07 (gh aw init, gh aw compile) and 08 (gh aw run).
  • 07 → 07d (model access) with an explicit return link to 07.

Cycles, feedback loops, weird cycles

All three are reported identically as cycle, feedback loop and weird cycle. None need a fix.

  1. 07-your-first-workflow ↔ 07d-confirm-model-access is intentional error recovery. 07d says "Arriving from step 07 (error recovery)... then return to Write Your First Agentic Workflow."
  2. 05-agentic-workflows-intro ↔ 05b-agentic-workflows-security is a mutual before/next pair. 05b requires 05, and 05 continues to 05b. The before edge back to 05 is only a "read first" prerequisite, so there is no real loop.
  3. 02a-setup-codespace ↔ side-quest-02-01-local-terminal are alternative setup paths that link to each other as fallbacks, not a circular dependency.

Verified ordering problem

1. Lock-file activity before any workflow exists
  • File reviewed: workshop/05-agentic-workflows-intro.md
  • Instruction that appears too early (line 53): "Activity 1 — identify the parts: Open any .lock.yml file in your repo and find the on: key." The code block below it says # Example: open .github/workflows/my-workflow.lock.yml. Checkpoint item: "You identified the on: key in a compiled .lock.yml file".
  • Missing prerequisite: The learner's practice repository has no .lock.yml at this point. Nothing in 01–04 creates one. 06-install-gh-aw.md installs gh-aw, and 07-your-first-workflow.md is where daily-report-status.lock.yml is first compiled.
  • Why it confuses or blocks: The learner is told to open a file that does not exist yet and must tick a checkpoint item they cannot complete. They may stop, think their setup is broken, or skip the activity.
  • Suggested fix: Either (a) change Activity 1 to point at a sample or embedded snippet in the page, or at the workshop repository's published example lock file, and reword the checkpoint to match; or (b) move the "open the .lock.yml and find on:" activity to the end of 07-your-first-workflow.md, after the first compile, and keep step 05 conceptual.
Reviewed and not flagged
  • side-quest-01-02-environment-reference.md: the page says "No terminal required to read this page." The gh --version check is an optional checkpoint, and the page notes the tools are in the Codespace. This is a reference side quest, not an ordering break.
  • Other missing_prerequisite_link items (05-SQ03, 08b, 09, 11-x, 13-x, 17-x and later): these are conceptual or reference pages, or later steps that sit after 06 and 07 in the main path, so gh aw is already available.

This issue is ready for an agent to resolve.

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

  • expires on Nov 21, 2026, 10:44 PM UTC
Lenguaje dominante
JavaScript
Estrellas
61
Forks
43
Merge medio
10 h 38 min
PR fusionados (30 d)
12

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.