[ordering-review] workshop order graph: 1 side-quest ordering issue, 3 benign cycles
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 1/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 88/100
- Tipo de issue
- Documentación
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- github-actions, markdown
- Área
- content, documentation
Línea de trabajo
Lee workshop/side-quest-01-02-environment-reference.md y workshop/README.md para confirmar dónde se desvía el side quest y cuándo se configura Codespace. Actualiza las instrucciones de verificación para que los alumnos sepan que deben ejecutar las comprobaciones después de completar la configuración de Codespace, y ajusta la nota sobre la rama en el README si corresponde. La tarea estará completa cuando se indique claramente a los alumnos que sigan el side quest antes de la configuración que traten la página como referencia hasta tener un Codespace.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Graph health summary
Reviewed 98 pages (3 dispatcher pages), 346 edges, 59 heuristic findings, 3 cycles, 3 feedback loops and 3 weird cycles. After verifying the cited pages, 58 findings are false positives (details below). One real ordering problem remains. The full generated graph and constraint list are in order-review-report.md from the run artifacts. The condensed core path is below.
graph TD
w00["00 welcome"] --> p01["01 prerequisites"]
p01 --> s02a["02a setup codespace"]
p01 -.->|branch| sq0102["01-SQ02 environment reference"]
p01 -.->|branch| sq0201["02-SQ01 local terminal"]
s02a --> a04["04 actions intro"]
sq0201 --> a04
a04 --> a05["05 agentic intro"]
a05 --> a05b["05b security"]
a05b --> a05c["05c practice"]
a05c --> i06["06 install gh-aw"]
i06 --> f07["07 first workflow"]
f07 --> m07d["07d model access"]
m07d --> r08["08 run workflow"]
r08 --> r08b["08b interpret run"]
r08b --> e09["09 agentic editing"]
Ordering constraints (key ones)
- 01 → 02a (Codespace) or 02-SQ01 (local) → 04 → 05 → 05b → 05c → 06 → 07 → 07d → 08 → 08b → 09
environment_ready,gh_installedandgh_authenticatedare provided by 02a (or 02-SQ01).gh awcommands require 06 (extension installed) and 07'sgh aw init.- 05/05b and 07/07d have reciprocal before/next edges (see cycles).
Cycles, feedback loops and weird cycles
All three are benign:
- 05 ↔ 05b – 05b says "You've read What Are Agentic Workflows?" and 05 says "Next: How Agentic Workflows Stay Safe". This is a normal prev/next pair, not a loop.
- 07 ↔ 07d – 07d deliberately has two entry points (error recovery from 07, or the normal next step), and 07 links to it for troubleshooting. This is documented intentionally.
- 02a ↔ 02-SQ01 – these are alternative environment paths (Codespace vs local) that reference each other as options, not a sequential loop.
The 51 missing_prerequisite_link findings (gh_authenticated not linked to 02a on later steps) are heuristic false positives. All those pages sit after 02a and 06 in the linear path, and 06/07 already state the prerequisites.
Verified ordering problem
File: workshop/side-quest-01-02-environment-reference.md
Instruction that appears too early (section "Verify your tools are ready"):
Open a terminal in your Codespace and run:
gh --version/git --version/gh auth status
Missing earlier step: The side quest branches from Step 1 (link unavailable: invalid HTTPS URL) (per workshop/README.md), but the Codespace is not created until 02a-setup-codespace.md. The page's own "Before You Start" says "No terminal required", yet the checkpoint section asks learners to open a Codespace terminal and run gh/gh auth status. It also says "If any command fails, see Set Up a Codespace", which points forward to a step the learner may not have done.
Why it confuses learners: A learner who follows the side quest right after Step 1 has no Codespace or terminal to open, so the verification looks broken or leads them to skip the check.
Suggested fix:
- Change the intro to: "Do this verification after you finish Set Up a Codespace (link unavailable: invalid HTTPS URL); until then, treat this page as read-only reference."
- Replace "Open a terminal in your Codespace and run:" with "After completing Set Up a Codespace, open its terminal and run:".
- Optionally move the README branch note to "branches from Step 2a".
This issue is ready for an agent to resolve.
Generated by 🧭 Workshop Order Review · copilot · auto · ~27 AIC · ⌖ ~1 AIC · ⊞ 4.8K · ◷
- expires on Nov 17, 2026, 11:07 AM UTC
- Lenguaje dominante
- JavaScript
- Estrellas
- 62
- Forks
- 43
- Merge medio
- 11 h 26 min
- PR fusionados (30 d)
- 13
Preparar el entorno
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
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de githubnext/gh-aw-workshop
-
curriculum documentation quality
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
githubnext/gh-aw-workshop#5779 ·
Los mantenedores suelen responder en 1 día
-
curriculum documentation quality
Dificultad 2/5 1-3 horas Aptitud para principiantes 87/100
githubnext/gh-aw-workshop#5780 ·
Los mantenedores suelen responder en 1 día
-
curriculum documentation quality
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
githubnext/gh-aw-workshop#5777 ·
Los mantenedores suelen responder en 1 día
-
curriculum documentation quality
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
githubnext/gh-aw-workshop#5776 ·
Los mantenedores suelen responder en 1 día
-
curriculum documentation quality
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
githubnext/gh-aw-workshop#5774 ·
Los mantenedores suelen responder en 1 día
Todos los issues de githubnext/gh-aw-workshop
Issues similares
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 69/100
Los mantenedores suelen responder en 1 día
-
automation chore ci-cd consistency developer-experience difficulty: easy discoverability documentation enhancement github-actions good first issue help wanted hygiene priority: P3 seo shell yaml
Dificultad 1/5 Menos de una hora Aptitud para principiantes 76/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
swc-project/swc-next-issues#394 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
adobe/helix-tools-website#480 ·
Los mantenedores suelen responder en 1 día
-
area: docs area: tests bug cloudflare cloudflare-workers consistency developer-experience difficulty: easy dx good first issue help wanted hygiene javascript priority: P3 quality tech: javascript tests
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
flisk-sh/readme-diagram#11 ·