[workshop-sim] Improve: Strengthen Step 8 checkpoint with pre-flight verification

Aperta
#5,519 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à
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
68/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions, markdown
Ambito
documentation

Direzione di ricerca

Start with 08-run-your-workflow.md and review its existing pre-flight section, checkpoint, and the Step 7 requirements described in the issue. Add checkpoint and prediction exercises for the .md and .lock.yml files, billing permission or secret, run log, and created issue. Confirm the shared curriculum score and learning KPI stay flat or improve while preserving or strengthening hands-on practice and scaffolding.

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

Descrizione

feedback simulation workshop

Problem: 08-run-your-workflow.md depends on Step 7 state (compiled, pushed lock file, matching billing). It has a pre-flight section, but the checkpoint omits it and covers only the UI run. Active learning is low (3.0) and the page is the 6th-lowest scoring (5.67). Baseline replay attributed all Step 8 failures to workflow-not-compiled.

Proposed change: Add checkpoint items that verify both .md and .lock.yml exist on main and that the permission or secret matches the chosen billing path. Add an exercise asking the learner to predict the run outcome, then compare it with the log, and to locate the created issue.

Failure mode: access barrier (state readiness), with a learning component

Quantitative guardrail: current overall_score 5.67; weakest dimension checkpoint_quality 0.0; active_learning 3.0, checkpoint_quality 0.0, scaffolding 5.0 (KPI 2.43). Added verification and prediction raise all three learning dimensions while keeping the same cognitive load.

Acceptance criteria:

  • The shared curriculum overall_score for the affected step stays flat or improves
  • The step's learning KPI index (2.0 × active_learning + 2.0 × checkpoint_quality + 1.5 × scaffolding) / 5.5 stays flat or improves
  • Hands-on practice, checkpoints, and scaffolding are preserved or strengthened

Suggested owner: copilot coding agent

Generated by 🔬 Workshop Student Simulator · copilot · auto · ~36 AIC · ⌖ ~1 AIC · ⊞ 15.4K · ◷

  • expires on Nov 10, 2026, 9:04 AM 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.