Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

クローズ 初心者向け
  • 何か問題がありますか？
#4,456 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
2/5
見積もり時間
1〜3時間
初心者へのやさしさ
78/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
github-actions, javascript, markdown
領域
content, documentation

調査の方向性

04-github-actions-intro.mdを開き、既存の「Reveal the labels」ブロックと、挿入箇所の前後にある2つのアクティビティを読みます。「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
スター
55
フォーク
36
平均マージ
2日 8時間
マージ済み PR（30日）
17

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

  • Dockerfile・Docker Compose ファイルなし
  • プルリクエストのテンプレートなし
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

githubnext/gh-aw-workshop のほかの issue

githubnext/gh-aw-workshop の issue をすべて見る

似ている issue

JavaScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。