[workshop-sim] Improve: Add intermediate recall checkpoint to reduce concept-overload dropout in 04-github-actions-intro.md

已关闭 适合新手
  • 哪里不对？
#4,456 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 3 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
78/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
github-actions, javascript, markdown
领域
content, documentation

调研方向

打开 04-github-actions-intro.md，阅读现有的“Reveal the labels”区块，以及拟插入位置前后的两个活动。在“Label a sample workflow”和“Try it: Explore a real workflow”之间，按照页面现有的显示答案模式，添加一个包含 3–4 个问题的回忆检查。完成标准是所有现有活动和页面末尾的检查点保持不变，且新检查遵循相同模式。

由索引模型根据 Issue 内容生成。

描述

feedback simulation workshop
Problem statement

04-github-actions-intro.md is the lowest-scoring step in the curriculum (overall_score 5.39/10) and has the highest conditional dropout rate among the five lowest-score candidates (14.6% among 44,163 at-risk runs, with concept-overload as the dominant failure category). The page introduces five new vocabulary terms (trigger, job, runner, step, action) in one pass, then stacks three separate labeling/exploration activities back-to-back ("Label a sample workflow," "Try it: Explore a real workflow," plus the earlier annotated example) with no intermediate checkpoint or recall check between them before the single end-of-page checkpoint. active_learning scores only 3.9/10 despite the activities present, because density of distinct practice opportunities per unit of new-concept load is low relative to peers.

Proposed change

Insert one short, low-friction recall checkpoint (3-4 question self-check, similar in format to the existing "Reveal the labels" <details> block) between the "Label a sample workflow" activity and the "Try it: Explore a real workflow" activity, so learners consolidate the five core terms before applying them in a live-repository context. Do not remove or shorten any existing activity — this is additive scaffolding, not simplification.

Failure mode classification

Learning barrier (conceptual density / insufficient intermediate scaffolding, not an access or tooling issue — no auth, environment, or terminal friction is involved in this step).

Quantitative guardrail

Current scores for 04-github-actions-intro.md: overall_score 5.39/10, cognitive_load 6.8, readability 10.0, active_learning 3.9, checkpoint_quality 0.0 (see companion checkpoint-regex repair issue), scaffolding 5.0, style_compliance 10.0 → learning KPI index = (2.0×3.9 + 2.0×0.0 + 1.5×5.0)/5.5 = 2.78/10. Adding one additional low-friction recall check increases activity_density (and therefore active_learning, which is scored as min(10, activity_density * 3.3)), without adding new prose or increasing word_count/new_concepts meaningfully, so cognitive_load should not worsen. The proposed change should raise overall_score and the learning KPI index, never lower them, and must not remove the existing three activities or any checkpoint content.

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, specifically via a measurable increase in active_learning from the added recall check
  • All three existing hands-on activities (annotated example, "Label a sample workflow," "Try it: Explore a real workflow") and the end-of-page checkpoint are preserved unchanged — the new recall check is inserted between activities, not a replacement for any of them
  • The new recall check uses the same <details>/reveal-answer pattern already used elsewhere on the page, so it does not introduce new UI conventions
Suggested owner

copilot coding agent (bounded content insertion with a clear existing pattern to follow; low judgment risk)
Related to #4453

Generated by 🔬 Workshop Student Simulator · copilot · auto · 236.2 AIC · ⌖ 7.07 AIC · ⊞ 15.1K · ◷

  • expires on Oct 12, 2026, 8:03 AM UTC
主要语言
JavaScript
星标
58
派生
40
平均合并
4 天 4 小时
30 天内合并 PR
8

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

githubnext/gh-aw-workshop 的其他 Issue

查看 githubnext/gh-aw-workshop 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。