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

[workshop-sim] Repair: Add mid-page formative checkpoint to GitHub Actions intro (04-github-actions-intro.md)

Cerrado Apto para principiantes
#4,368 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
74/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions, markdown

Línea de trabajo

El cambio va en 04-github-actions-intro.md, justo después del bloque desplegable "Label a sample workflow" y antes de "Try it: Explore a real workflow". Lee el patrón de respuestas desplegables de alrededor para que el nuevo cuestionario de repaso de 2-3 preguntas use el mismo formato. Está terminado cuando el cuestionario se inserta con desplegables en línea, el diagrama existente, la tabla comparativa, la actividad "Try it" y la lista de verificación final no cambian, y npx --yes markdownlint-cli2 "**/*.md" no informa de errores nuevos.

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

Descripción

feedback simulation workshop

Problem statement

04-github-actions-intro.md is the lowest-scoring curriculum step overall (overall_score 5.39/10) and the #2 highest-failure step in the Monte Carlo simulation (7,231 failures across 1,000×46 runs, 16.4% conditional dropout among 44,183 at-risk runs). The failure category is 100% concept-overload: the page introduces 28 new concepts in one pass (word_count 756, 36 inline commands, 7 h2 sections) with no checkpoint or formative check between the "Label a sample workflow" activity and the following "Try it: Explore a real workflow" section. Learners — especially beginner/no-coding and github-basic personas — accumulate misunderstandings that compound into Step 5 (05-agentic-intro), the next-highest-dropout step.

Proposed change

Insert one short self-check immediately after the "Label a sample workflow" reveal-the-labels <details> block (before "Try it: Explore a real workflow"): a 2-3 item recall quiz ("Which key starts a workflow? Which key names the machine?") with an inline reveal, so learners catch labeling mistakes before moving to the live-repo activity. Do not remove or shorten the existing anatomy diagram, classic-vs-agentic comparison table, or the "Try it" browser activity — all of those are appropriately challenging content, not noise.

Failure mode classification: Learning barrier (conceptual density / insufficient mid-page scaffolding, not an access or tooling issue).

Quantitative guardrail

  • Current overall_score: 5.39/10
  • Weakest rubric dimensions: checkpoint_quality 0.0/10 (shared detection gap across all 30 steps — see report), active_learning 3.9/10
  • Current learning KPI index for this step: (2.0×3.9 + 2.0×0.0 + 1.5×5.0) / 5.5 = 2.78/10 (active_learning 3.9, checkpoint_quality 0.0, scaffolding 5.0)
  • The proposed change adds one more hands-on recall activity (raising active_learning) without touching readability, cognitive_load, or style_compliance, and should not lower scaffolding since it adds a support point rather than removing one. It should raise, not lower, overall_score and the learning KPI index.

Acceptance criteria

  • The shared curriculum quantitative assessment overall_score for 04-github-actions-intro.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
  • The existing "Label a sample workflow" and "Try it" hands-on activities, the reveal-answer checkpoints, and the end-of-page ## :white_check_mark: Checkpoint checklist are preserved or strengthened, not removed or shortened
  • Markdown passes npx --yes markdownlint-cli2 "**/*.md" with no new errors

Suggested owner: workshop maintainer
Related to #4367

Generated by 🔬 Workshop Student Simulator · copilot · auto · 163.7 AIC · ⌖ 12.2 AIC · ⊞ 15.1K · ◷

  • expires on Oct 10, 2026, 7:10 AM UTC
Lenguaje dominante
JavaScript
Estrellas
53
Forks
35
Merge medio
1 d 6 h
PR fusionados (30 d)
15

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.