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

Abierto
  • ¿Algo no está bien?
#5,519 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
68/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions, markdown
Área
documentation

Línea de trabajo

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.

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

Descripción

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
Lenguaje dominante
JavaScript
Estrellas
58
Forks
40
Merge medio
1 d 22 h
PR fusionados (30 d)
7

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.