Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[workshop-sim] Repair: Fix checkpoint-quality regex in curriculum_assessment.py to recognize :white_check_mark: shortcode headings

已关闭 适合新手
#4,249 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
78/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
markdown, python
领域
testing, tooling

调研方向

从.github/skills/curriculum-quantitative-assessment/curriculum_assessment.py开始,检查CHECKPOINT_RE和score_checkpoint_quality()的测试。使用工作坊文件运行评估,并确认包含字面字符✅的标题和包含:white_check_mark:的标题都能被检测到。完成标准是:根据检查清单内容为检查点评分,群组的Learning KPI有所提升,并且工作坊内容没有任何更改。

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

描述

feedback simulation workshop
Problem statement

.github/skills/curriculum-quantitative-assessment/curriculum_assessment.py scores checkpoint_quality as 0.0/10 for all 30 main workshop steps, even though every step (confirmed on 04-github-actions-intro.md, 07-your-first-workflow.md, 07d-confirm-model-access.md, 08-run-your-workflow.md, and others) ends with a properly formatted ## :white_check_mark: Checkpoint section containing a markdown checklist, exactly as required by AGENTS.md. The detection regex CHECKPOINT_RE = re.compile(r"##\s+✅\s*Checkpoint", re.IGNORECASE) only matches the literal unicode ✅ emoji character, but the workshop's actual convention (and AGENTS.md's own documented style) uses the GitHub Markdown shortcode :white_check_mark:. This silently zeroes out one-third of the weight in the Learning KPI index (checkpoint_quality carries a 2.0 weight alongside active_learning) for every single page in the corpus, masking genuine scaffolding and making the Learning KPI index (currently 2.87/10) artificially pessimistic.

Proposed change

Update CHECKPOINT_RE to also match the :white_check_mark: shortcode form, e.g.:

CHECKPOINT_RE = re.compile(
    r"##\s+(?:✅|:white_check_mark:)\s*Checkpoint", re.IGNORECASE
)

Re-run the assessment script against all workshop files and confirm has_checkpoint becomes True and checkpoint_quality is scored on its actual content-quality criteria (not zeroed) for every page with a real checkpoint section.

Failure mode classification

Learning barrier (measurement defect) — this is not a dropout-causing problem for learners, but it is a content-quality measurement gap that misrepresents the curriculum's actual scaffolding quality and would misdirect future repair priorities if left uncorrected.

Quantitative guardrail

Current cohort-wide values: checkpoint_quality mean 0.0/10 across all 30 steps (every step affected identically), Learning KPI index (2.0×4.15 + 2.0×0.0 + 1.5×5.0)/5.5 ≈ 2.87. After the regex fix, checkpoint_quality should rise from its artificial floor to reflect each step's actual checklist quality (item count, specificity, actionability per score_checkpoint_quality), and the Learning KPI index should rise correspondingly — this is a pure correction, not a content change, so overall_score per step should only increase or stay flat, never decrease, since no step currently benefits from the broken regex.

Acceptance criteria
  • The shared curriculum quantitative assessment overall_score for every step with an existing :white_check_mark: Checkpoint heading stays flat or improves after the regex fix
  • The cohort-wide Learning KPI index ((2.0 × active_learning + 2.0 × checkpoint_quality + 1.5 × scaffolding) / 5.5) improves measurably once checkpoint_quality is no longer artificially zeroed
  • No existing checklist items, checkpoints, or scaffolding content are touched — this is a scoring-tool fix only, not a workshop content change
  • score_checkpoint_quality() unit tests (new or existing) confirm both the unicode ✅ and :white_check_mark: shortcode forms are detected
Suggested owner

copilot coding agent (small, well-scoped regex fix with an existing test harness in curriculum_assessment.py)
Related to #4247

Generated by 🔬 Workshop Student Simulator · copilot · auto · 246.5 AIC · ⌖ 8.13 AIC · ⊞ 15.1K · ◷

  • expires on Oct 7, 2026, 9:06 AM UTC
主要语言
JavaScript
星标
52
派生
26
平均合并
11 小时 32 分钟
30 天内合并 PR
22

环境准备

在 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 摘要。