[workshop-sim] Improve: Add recovery scaffolding to the GitHub Actions intro labeling exercise
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions
- Domain
- ci-cd, documentation
Research direction
Start by reading 04-github-actions-intro.md and locate the "Label a sample workflow" exercise. Review the surrounding skip-ahead and real-workflow activities before adding the recovery aid. Re-run the workshop student simulator and quantitative assessment; done means the existing activities remain and the scores stay flat or improve, with fewer concept-overload failures.
Written by the indexing model from the issue text.
Description
Problem statement
04-github-actions-intro.md has both the lowest curriculum quality score in the corpus (5.39/10) and the highest raw failure count in the simulated core path (7,982 dropouts, all categorized as concept-overload). The step introduces 28 new concepts (per the rubric's new_concepts metric) with a troubleshootingSupport signal of 0 and a checkpoint_quality rubric score of 0.0/10 — learners who get lost in the trigger/job/runner/step/action vocabulary during the labeling exercise have no in-page guidance to recover, only a plain unchecked checklist at the end.
Proposed change
Add a short, structured troubleshooting/recovery aid immediately after the "Label a sample workflow" exercise — for example, a <details> block offering a worked walkthrough of one mislabeled term with an explanation of why it's that category, for learners who could not complete the exercise unaided. Do not remove the existing exercise, the "already know GitHub Actions" skip-ahead path, or the "Try it: Explore a real workflow" activity — all three already contribute positively to active_learning and should be preserved.
Failure mode classification
Learning barrier (conceptual density combined with a checkpoint_quality score of 0.0 and no recovery scaffolding — not an access/tooling issue, since this page requires no terminal or credentials).
Quantitative guardrail
Current scores for 04-github-actions-intro.md:
overall_score: 5.39/10 (lowest in the 30-step corpus)- Weakest rubric dimensions:
checkpoint_quality(0.0/10),active_learning(3.9/10) - Learning KPI index:
(2.0 × 3.9 + 2.0 × 0.0 + 1.5 × 5.0) / 5.5= 2.78/10
The proposed recovery aid directly targets checkpoint_quality (by giving learners a way to self-verify and correct their labeling exercise) without reducing active_learning or scaffolding, since the exercise itself and its concepts remain unchanged. This should raise, not lower, the step's overall_score and learning KPI index.
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 - The existing labeling exercise, skip-ahead path, and "explore a real workflow" activity are preserved or strengthened — not removed or simplified to inflate completion
- Re-running the workshop student simulator shows a reduced
concept-overloadfailure count at04-actions-introwithout shrinking at-risk attempts at downstream steps
Suggested owner
workshop maintainer
Related to #3962
Generated by 🔬 Workshop Student Simulator · copilot · auto · 174.2 AIC · ⌖ 8.32 AIC · ⊞ 14.8K · ◷
- expires on Sep 30, 2026, 7:13 AM UTC
- Dominant language
- JavaScript
- Stars
- 51
- Forks
- 23
- Avg merge
- 9h 44m
- 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
-
feedback simulation workshop
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/gh-aw-workshop#4007 ·
Maintainers usually reply within 1 day
-
documentation guidelines
Difficulty 1/5 Under an hour Newbie friendliness 92/100
githubnext/gh-aw-workshop#4003 ·
Maintainers usually reply within 1 day
-
documentation guidelines
Difficulty 1/5 Under an hour Newbie friendliness 92/100
githubnext/gh-aw-workshop#4002 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 95/100
githubnext/gh-aw-workshop#3986 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
githubnext/gh-aw-workshop#3980 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
opensearch-project/security-dashboards-plugin#2543 ·
Maintainers usually reply within 1 day
-
[quality] refresh-radar-reports.yml runs on ubuntu-latest while every other job pins ubuntu-24.04Openagent/quality hive/hosted-available-lke648397-260827-5n31 quality testing
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
godotengine/godot-website#1432 ·
-
Add: Mooz RetroOpenchannels:add check:passed
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day