[workshop-sim] Improve: Split GitHub Actions in 5 Minutes into two checkpoints to reduce concept-overload dropout
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions
- Domain
- documentation
Research direction
Start in 04-github-actions-intro.md by locating the existing end-of-page checklist and the "Label a sample workflow" exercise. Split the five existing checklist items so an intermediate scored checkpoint follows that exercise, while retaining the final checkpoint. Run the shared curriculum quantitative assessment and confirm the listed learning metrics stay flat or improve.
Written by the indexing model from the issue text.
Description
Problem statement
04-github-actions-intro.md is the lowest-scoring step in the entire 30-step curriculum (overall_score 5.39/10) and the fourth-highest-dropout step (15.92% conditional dropout among 44,183 at-risk runs), with concept-overload as the dominant failure category. The page packs a YAML refresher, a labeling exercise, a classic-vs-agentic comparison table, and a "find a real workflow" browser activity into one pass, and like the other low scorers, it has checkpoint_quality 0.0 — only a single end-of-page checklist with no intermediate check after the YAML/labeling section before introducing the classic-vs-agentic comparison.
Proposed change
Split the page's existing single checklist into two scored checkpoints: one immediately after the "Label a sample workflow" exercise (confirming the learner can identify on/jobs/steps/runs-on before introducing agentic concepts), and the existing final checklist for the full page. This is a sequencing/scaffolding change, not a content reduction — all five existing checkpoint items remain, split across two checkpoints instead of bunched at the end.
Failure mode classification
Learning barrier — concept-overload combined with zero checkpoint_quality points to a pacing/scaffolding gap rather than a tooling or environment barrier (this page explicitly requires no terminal or credentials).
Quantitative guardrail
Current scores for 04-github-actions-intro.md: overall_score 5.39/10, active_learning 3.9, checkpoint_quality 0.0, scaffolding 5.0 → learning KPI index 2.24/10. Splitting the existing checklist into two scored checkpoints should raise checkpoint_quality (currently 0.0 across the whole curriculum) and should not lower active_learning, scaffolding, overall_score, or the KPI index, since no existing activity or checklist item is removed.
Acceptance criteria
- The shared curriculum quantitative assessment
overall_scorefor04-github-actions-intro.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 - Hands-on practice, checkpoints, and scaffolding are preserved or strengthened (not removed or weakened to chase completion numbers)
- An intermediate checkpoint exists after the "Label a sample workflow" exercise, distinct from the existing end-of-page checklist, and all five original checklist items are retained across the two checkpoints
Suggested owner
copilot coding agent
Related to #4087
Generated by 🔬 Workshop Student Simulator · copilot · auto · 197.6 AIC · ⌖ 7.17 AIC · ⊞ 15.1K · ◷
- expires on Oct 3, 2026, 9:02 AM UTC
- Dominant language
- JavaScript
- Stars
- 52
- Forks
- 26
- Avg merge
- 12h 54m
- Merged PRs (30d)
- 17
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from githubnext/gh-aw-workshop
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
githubnext/gh-aw-workshop#4417 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
githubnext/gh-aw-workshop#4416 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 78/100
githubnext/gh-aw-workshop#4413 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/gh-aw-workshop#4410 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/gh-aw-workshop#4411 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
chore v2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
modelcontextprotocol/servers#5115 ·
Maintainers usually reply within 1 day
-
beginner bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 85/100
philaconvalley/website#168 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
druxt/umami.demo.druxtjs.org#527 ·
Maintainers usually reply within 9 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
NuSkooler/enigma-bbs#907 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100