[ordering-review] workshop order graph: 1 confirmed ordering issue, no true cycles

Aperta Adatta ai principianti
  • Qualcosa non va?
#5,499 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
77/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github, github-actions, javascript
Ambito
content, documentation

Direzione di ricerca

Leggi workshop/05-agentic-workflows-intro.md, poi esamina workshop/06-install-gh-aw.md e workshop/07-your-first-workflow.md per confermare quando gli studenti ottengono per la prima volta un file .lock.yml. Aggiorna l’attività e il checkpoint in modo che possano essere completati in questa fase, usando un file di esempio oppure spostando più avanti l’attività pratica. Il lavoro è terminato quando la lezione non chiede più agli studenti di aprire un file che non hanno ancora creato.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

Reviewed 97 workshop pages (338 edges, 57 heuristic findings, 3 cycles, 3 weird cycles, 0 self loops). After checking the cited files, one real ordering problem is confirmed. The cycles are intentional or heuristic artifacts, and the other 49 missing_prerequisite_link findings are false positives from the capability heuristic.

Mermaid graph (core path, condensed from the generated graph)

graph TD
  n00["00 Welcome"] --> n01["01 Prerequisites"]
  n01 --> n02a["02a Set Up a Codespace"]
  n02a --> n04["04 GitHub Actions intro"]
  n04 --> n05["05 What are agentic workflows"]
  n05 --> n05b["05b Security"]
  n05b --> n05c["05c Practice"]
  n05c --> n06["06 Install gh-aw"]
  n06 --> n07["07 First workflow"]
  n07 --> n07d["07d Confirm model access"]
  n07d --> n08["08 Run workflow"]
  n08 --> n08b["08b Interpret run"]
  n08b --> n09["09 Agentic editing"]
  n09 --> n14["14 Next steps"]
  n07d -.error recovery.-> n07

The full generated graph is in the run artifact /tmp/gh-aw/data/order-review-report.md.

Ordering constraints (core path)

  • 00 → 01 → 02a (Codespace and terminal ready) → 04 → 05 → 05b → 05c → 06 (install gh aw, gh aw init, push skills) → 07 → 07d → 08 → 08b → 09.
  • gh aw commands require 06. .lock.yml files require 07.
  • 08 requires 07d. 09 requires a completed run from 08/08b.
  • Side quests hang off these core steps and require the environment from 02a.

Cycles, feedback loops and weird cycles

  • 07 ⇄ 07d: not a defect. 07d documents two entry points, "error recovery" from 07 and "normal flow" after 07. 07 sends learners to 07d only on failure. No change needed.
  • 05 ⇄ 05b: false positive. 05b only says "You've read What Are Agentic Workflows?", and 05 links forward to 05b.
  • 02a ⇄ side-quest-02-01-local-terminal: false positive from capability edges. The side quest is an alternative local path, and 02a does not depend on it.
  • side-quest-01-02-environment-reference.md was flagged for using gh aw and gh --version before 02a. It states "No terminal required to read this page", so this is a false positive.

Verified ordering problem

workshop/05-agentic-workflows-intro.md: asks for a .lock.yml file before any exists
  • Quoted instruction: "Activity 1 — identify the parts: Open any .lock.yml file in your repo and find the on: key."
  • Related too-early commands: The page also tells the learner "gh aw compile generates it from the .md" and lists "You identified the on: key in a compiled .lock.yml file" in the Checkpoint. This is while learners only have a freshly created my-agentic-workflows repo.
  • Missing prerequisite: The gh aw extension is installed in 06-install-gh-aw.md. The first workflow and its .lock.yml are created in 07-your-first-workflow.md. The page's Before You Start only requires 04-github-actions-intro.md.
  • Why it confuses or blocks: A learner at this point has no workflow files in their repo, so the activity and checkpoint item cannot be completed. They may think setup failed or may look for a file that does not exist yet.
  • Suggested fix: Either change Activity 1 to inspect a sample or linked .lock.yml, such as an example in the gh-aw docs or a snippet embedded in the page. Or move the "open your own .lock.yml" activity and its checkpoint item to 07-your-first-workflow.md or 08b-interpret-your-run.md. Keep the concept-only checkpoint item ("You know that gh aw compile generates .lock.yml from the .md source").

Dismissed heuristic findings

The other missing_prerequisite_link findings flag gh_authenticated for many pages (07, 08, 09, 15–30, and so on). Their Before You Start sections link to the previous step in the chain, which transitively depends on 02a and 06, so these are false positives.

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 9, 2026, 10:44 PM UTC
Lingua principale
JavaScript
Stelle
58
Fork
40
Merge medio
1g 22h
PR unite (30g)
7

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di githubnext/gh-aw-workshop

Tutte le issue di githubnext/gh-aw-workshop

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.