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

[workshop-sim] Repair: Front-load Copilot access/billing pre-check in Step 7

Cerrado Apto para principiantes
  • ¿Algo no está bien?
#4,494 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
77/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github, github-actions
Área
documentation

Línea de trabajo

Empieza con 07-your-first-workflow.md y lee la explicación existente sobre las rutas de facturación en side-quest-07d-billing-paths.md. Añade un aviso al principio, antes de “Create your first workflow”, que enlace a github.com/settings/copilot y pregunte si la facturación centralizada de Copilot para GitHub Actions está habilitada para el repositorio. Mantén las comprobaciones y actividades existentes y, después, confirma que las puntuaciones de la evaluación compartida y el KPI de aprendizaje no disminuyan.

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

Descripción

feedback simulation workshop

Problem statement

Step 07-first-workflow (mapped to 07-your-first-workflow.md + 07d-confirm-model-access.md) is now the single highest-dropout step in the workshop at 21.4% conditional dropout (4,892 of 22,842 at-risk simulated runs), dominated by the copilot-access-missing failure category (4,109 of those failures). Learners reach the model-access verification prompt (gh copilot / /agentic-workflows ...) before they discover whether their account actually has usable Copilot access or an active centralized-billing arrangement — so the cost of discovering the blocker is paid only after they have already started authoring the workflow file.

Proposed change

Add an earlier, lightweight Copilot-access/billing pre-check at the very top of 07-your-first-workflow.md (before "Create your first workflow"), pointing directly to github.com/settings/copilot and the billing-path decision ("Is centralized Copilot billing for GitHub Actions enabled for this repository?") that currently only appears later, inside side-quest-07d-billing-paths.md. Keep the existing in-page checks intact; this is additive front-loading, not a replacement.

Failure mode classification

Access barrier (account entitlement / billing configuration, not a conceptual or scaffolding gap).

Quantitative guardrail

Current scores for 07-your-first-workflow.md:

  • overall_score: 6.25/10
  • Weakest rubric dimension: checkpoint_quality (0.0/10)
  • Learning KPI index: 3.65/10 (active_learning 6.3, checkpoint_quality 0.0, scaffolding 5.0)

This change only adds an early pre-check callout; it does not touch the existing activity density, checklist items, or prerequisite section, so active_learning, scaffolding, and checkpoint_quality — and therefore overall_score and the learning KPI index — should stay flat or improve as a side effect of any later checkpoint-detection fix, never decrease.

Acceptance criteria

  • The shared curriculum quantitative assessment overall_score for 07-your-first-workflow.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 (the existing Copilot CLI test-prompt activity and checklist) are preserved or strengthened, not removed or weakened
  • The new pre-check callout links to both github.com/settings/copilot and the billing-path decision question, and appears before the "Create your first workflow" section

Suggested owner

workshop maintainer
Related to #4493

Generated by 🔬 Workshop Student Simulator · copilot · auto · 309.7 AIC · ⌖ 14.8 AIC · ⊞ 15.1K · ◷

  • expires on Oct 13, 2026, 8:28 AM UTC
Lenguaje dominante
JavaScript
Estrellas
53
Forks
35
Merge medio
1 d 5 h
PR fusionados (30 d)
16

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.