Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[workshop-sim] Repair: Make Step 7d billing-path completion state explicit and verifiable before Step 8

Cerrado Apto para principiantes
  • ¿Algo no está bien?
#4,454 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
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
68/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github, javascript
Área
content, documentation

Línea de trabajo

Lee 07d-confirm-model-access.md y compara el punto de control del paso 7d con las opciones de facturación y la configuración de side-quest-07d-billing-paths.md. Añade un elemento de lista de comprobación independiente que pida a los alumnos identificar su ruta de facturación y verificar los permisos o la configuración de secretos correspondientes en daily-report-status.lock.yml, con instrucciones para volver a compilar, hacer commit y push si es necesario. La tarea estará terminada cuando la página permita a los alumnos confirmar que el archivo lock coincide con la ruta elegida antes del paso 8 y se cumplan las salvaguardas de evaluación indicadas.

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

Descripción

feedback simulation workshop
Problem statement

08-run-your-workflow.md has a 100% conditional dropout rate in the latest Monte Carlo simulation (17,652 at-risk runs). The content gate requires a compiled and pushed .lock.yml whose billing configuration matches the learner's chosen path (organization centralized billing vs. personal COPILOT_GITHUB_TOKEN). That choice is made entirely inside side-quest-07d-billing-paths.md, while 07d-confirm-model-access.md only links out to it ("Follow the full setup steps in Side Quest: Copilot Billing Paths, then return here once your workflow file and lock file are committed") and never states which path was taken or re-confirms the resulting permissions block on the main path. This is an access barrier: the content does not let the learner (or the simulator) confirm the prerequisite state before advancing.

Proposed change

Add an explicit, on-page confirmation step at the end of 07d-confirm-model-access.md (not buried only in the side quest) that has the learner:

  1. State which billing path they chose (organization centralized vs. personal).
  2. Open daily-report-status.lock.yml and visually confirm the permissions.copilot-requests / secret configuration matches that choice.
  3. Recompile, commit, and push if anything doesn't match.
    Add this confirmation as its own checklist item in the Step 7d checkpoint, distinct from the generic "I chose a billing path and completed all configuration steps" line, so it is independently verifiable both by learners and by future content audits.
Failure mode classification

Access barrier (environment/configuration state-tracking gap, not conceptual difficulty).

Quantitative guardrail

Current 07d-confirm-model-access.md rubric: overall_score 6.25/10, active_learning 6.3, checkpoint_quality 0.0, scaffolding 5.0 → learning KPI index = (2.0×6.3 + 2.0×0.0 + 1.5×5.0)/5.5 = 3.65/10. Adding an explicit verification sub-step increases active, hands-on checking (raises active_learning) and strengthens the existing checkpoint without removing any current content, so overall_score and the KPI index should hold flat or rise. No scaffolding or prerequisite content is removed.

Acceptance criteria
  • The shared curriculum quantitative assessment overall_score for 07d-confirm-model-access.md stays flat or improves after the change
  • 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 (the new verification sub-step is additive, not a replacement for existing guidance)
  • A learner following only 07d-confirm-model-access.md (without re-reading the side quest) can state with certainty which billing path is active and that the lock file matches it, before proceeding to Step 8
Suggested owner

workshop maintainer (content restructuring across two linked files; needs judgment about which checklist wording avoids duplicating the side quest)
Related to #4453

Generated by 🔬 Workshop Student Simulator · copilot · auto · 236.2 AIC · ⌖ 7.07 AIC · ⊞ 15.1K · ◷

  • expires on Oct 12, 2026, 8:03 AM UTC
Lenguaje dominante
JavaScript
Estrellas
53
Forks
35
Merge medio
13 h 50 min
PR fusionados (30 d)
14

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.