[workshop-sim] Improve: Add a mid-page concept checkpoint to 04-github-actions-intro.md
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, markdown
- Domain
- content
Research direction
Read 04-github-actions-intro.md, especially the Quick Refresher, the agentic-vs-classic comparison, and the existing exercises. Add a short recall prompt between the refresher and comparison that checks the five named fundamentals, while preserving the existing activities and end checklist. Done means the prompt is in that location and both quantitative assessment measures stay flat or improve.
Written by the indexing model from the issue text.
Description
Problem statement
04-github-actions-intro.md (simulator step 04-actions-intro) has the lowest curriculum quality overall_score in the entire 30-step corpus (5.39/10) and the third-highest conditional dropout rate (16.9% among 44,143 at-risk runs, 95% interval 16.6%–17.3%). 100% of failures at this step are categorized as concept-overload (7,465 failures) — there is no auth, tooling, or billing friction involved. The page introduces 28 new concepts (trigger, job, runner, step, action, self-hosted runner, plus a full agentic-vs-classic comparison table) with only a single label/reveal exercise and an "already know this? skip ahead" escape hatch as reinforcement, and zero checkpoints occur before the end of the page.
Proposed change
Insert one additional "concept checkpoint" roughly midway through the page — immediately after the "Quick Refresher" section (trigger/job/steps + the annotated hello-workflow.yml example) and before the "Why This Matters for Agentic Workflows" comparison table. This mid-page checkpoint would ask the learner to self-verify the five foundational terms (on, jobs, steps, runs-on, workflow file location) with a short recall prompt, before introducing the agentic-vs-classic comparison and the "Label a sample workflow" activity. This splits one large 28-concept block into two smaller, separately verified chunks rather than removing any content.
Failure mode classification
Learning barrier — concept overload from cognitive load and insufficient mid-page scaffolding, not an access or tooling problem.
Quantitative guardrail
Current scores for 04-github-actions-intro.md:
overall_score: 5.39/10 (lowest in the corpus)- Weakest rubric dimensions:
active_learning3.9/10 andcheckpoint_quality0.0/10 - Learning KPI index for this step:
active_learning3.9,checkpoint_quality0.0,scaffolding5.0 → index = (2.0×3.9 + 2.0×0.0 + 1.5×5.0)/5.5 = 2.78/10
Adding a mid-page checkpoint directly targets active_learning (an additional self-check activity) and scaffolding (breaking one large concept block into two verified stages) without reducing the number of concepts taught or removing the existing "Label a sample workflow" / "Explore a real workflow" exercises. This should raise, not lower, both overall_score and the learning KPI index for this file.
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 for04-github-actions-intro.md - The existing "Label a sample workflow" exercise, "Explore a real workflow" browser activity, and end-of-page checklist are preserved unchanged (not removed or simplified)
- A new mid-page self-check / recall prompt is added after the Quick Refresher section and before the agentic-vs-classic comparison table, without reducing the number of concepts covered
Suggested owner
copilot coding agent
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
- Dominant language
- JavaScript
- Stars
- 51
- Forks
- 23
- Avg merge
- 10h 14m
- Merged PRs (30d)
- 25
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
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/gh-aw-workshop#4220 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
githubnext/gh-aw-workshop#4218 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
githubnext/gh-aw-workshop#4216 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
githubnext/gh-aw-workshop#4214 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#4198 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
automated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
lirantal/discoprint#36 ·
Maintainers usually reply within 1 day
-
accepting PR Content:HTML
Difficulty 1/5 Under an hour Newbie friendliness 88/100
mdn/content#45988 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
txn2/mcp-data-platform#2030 ·
Maintainers usually reply within 1 day
-
ci hacktoberfest help wanted size/small type/bug type/docs type/enhancement up-for-grabs
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Redo-San/RedoSan-Authenticity#527 ·
Maintainers usually reply within 1 day