[workshop-sim] Repair: Add an early Copilot-access gate before Step 7 workflow authoring
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
- 75/100
- Tipo de issue
- Documentación
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- github
- Área
- documentation
Línea de trabajo
Lee 06-install-gh-aw.md y el prompt de prueba existente de Copilot y la misión secundaria de resolución de problemas de acceso mencionada en el issue; compáralos con el flujo de Step 7 en 07-your-first-workflow.md. Añade antes del enlace “Next” de Step 6 una breve comprobación de acceso que se pueda omitir, con un enlace de recuperación, y conserva el contenido de Step 7. Se considera terminado si las puntuaciones de la evaluación compartida de Step 7 se mantienen o mejoran.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem statement
07-your-first-workflow.md (simulator step 07-first-workflow) is the single highest-dropout step in the workshop: 22.4% conditional dropout among 22,237 at-risk Monte Carlo runs (95% interval 21.9%–23.0%). The dominant failure category is copilot-access-missing (3,922 of 4,981 total failures at this step) — learners discover they lack a usable Copilot seat/license only after writing and compiling a full workflow, deep inside Step 7's authoring flow. The billing-method instructions themselves (Step 7d + the Copilot Billing Paths side quest) are sound and fully cover both centralized and personal billing configuration — but there is no early gate that checks basic Copilot reachability before the learner invests time in workflow authoring.
Proposed change
Add a short, mandatory Copilot-access check at the end of Step 6 (06-install-gh-aw.md), before the learner moves into Step 7's authoring flow. This reuses the existing test prompt pattern already present later in Step 7 (gh copilot + /agentic-workflows test prompt), moving the first instance of that check one step earlier so access problems surface before, not after, workflow authoring. Step 7 would keep its own confirmation as a safety net (defense in depth), rather than removing any existing verification.
Failure mode classification
Access barrier — this is purely an environment/licensing gap, not a conceptual gap. No change to workflow-authoring instructional content is implied.
Quantitative guardrail
Current scores for 07-your-first-workflow.md:
overall_score: 6.25/10- Weakest rubric dimension:
checkpoint_quality(0.0/10 — rubric detection artifact affecting all 30 steps equally, not specific to this file) - Learning KPI index for this step:
active_learning6.3,checkpoint_quality0.0,scaffolding5.0 → index = (2.0×6.3 + 2.0×0.0 + 1.5×5.0)/5.5 = 3.65/10
The proposed change only moves an existing verification step earlier in the curriculum sequence (into Step 6) and does not remove or weaken any existing Step 7 content, exercise, or checkpoint. It should therefore leave overall_score, active_learning, and the learning KPI index for 07-your-first-workflow.md flat or slightly improved (an earlier gate reduces wasted authoring effort for blocked learners without touching the instructional content that scores active_learning).
Acceptance criteria
- The shared curriculum quantitative assessment
overall_scorefor07-your-first-workflow.mdstays flat or improves after the change - The step's learning KPI index
(2.0 × active_learning + 2.0 × checkpoint_quality + 1.5 × scaffolding) / 5.5stays flat or improves for07-your-first-workflow.md - All existing hands-on practice, checkpoints, and scaffolding in Step 7 (the workflow-authoring prompt, compile/commit/push sequence, and existing checkpoint checklist) are preserved unchanged
-
06-install-gh-aw.mdgains a brief, skippable Copilot-access test prompt step before its existing "Next" link to Step 7, with a clear recovery link to the existing Copilot-access troubleshooting side quest
Suggested owner
workshop maintainer
Related to #4215
Generated by 🔬 Workshop Student Simulator · copilot · auto · 191.3 AIC · ⌖ 7.49 AIC · ⊞ 15.1K · ◷
- expires on Oct 6, 2026, 7:27 AM UTC
- Lenguaje dominante
- JavaScript
- Estrellas
- 55
- Forks
- 36
- Merge medio
- 2 d 8 h
- PR fusionados (30 d)
- 17
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
-
[workshop-sim] Improve: Strengthen practice and checkpoints in Step 05 (What Are Agentic Workflows?)Abiertofeedback simulation workshop
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
githubnext/gh-aw-workshop#4972 ·
Los mantenedores suelen responder en 1 día
-
feedback simulation workshop
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
githubnext/gh-aw-workshop#4971 ·
Los mantenedores suelen responder en 1 día
-
curriculum documentation quality
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
githubnext/gh-aw-workshop#4969 ·
Los mantenedores suelen responder en 1 día
-
curriculum documentation quality
Dificultad 2/5 Medio día Aptitud para principiantes 85/100
githubnext/gh-aw-workshop#4966 ·
Los mantenedores suelen responder en 1 día
-
curriculum documentation quality
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
githubnext/gh-aw-workshop#4964 ·
Los mantenedores suelen responder en 1 día
Todos los issues de githubnext/gh-aw-workshop
Issues similares
-
bug confirmed issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
open-webui/open-webui#33196 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
area: apple-music area: build-release bug effort: small priority: high
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
ChristianTabor/Argon#32 ·
Los mantenedores suelen responder en 1 día
-
0️⃣ phase/new
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100