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

[workshop-sim] Repair: Make Step 7d billing-path completion state explicit and verifiable before Step 8

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
68/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
github, javascript

调研方向

阅读 07d-confirm-model-access.md,并将步骤 7d 的检查点与 side-quest-07d-billing-paths.md 中的账单选项和配置进行比较。添加一个独立的清单项,要求学习者确认自己的账单路径,并验证 daily-report-status.lock.yml 中匹配的权限或 secret 设置,同时说明必要时如何重新编译、提交和推送。完成标准:在步骤 8 之前,页面能够让学习者确认 lock 文件与其选择的路径一致,并满足所述的评估防护要求。

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

描述

feedback simulation workshop
Problem statement

08-run-your-workflow.md has a 100% conditional dropout rate in the latest Monte Carlo simulation (17,652 at-risk runs). The content gate requires a compiled and pushed .lock.yml whose billing configuration matches the learner's chosen path (organization centralized billing vs. personal COPILOT_GITHUB_TOKEN). That choice is made entirely inside side-quest-07d-billing-paths.md, while 07d-confirm-model-access.md only links out to it ("Follow the full setup steps in Side Quest: Copilot Billing Paths, then return here once your workflow file and lock file are committed") and never states which path was taken or re-confirms the resulting permissions block on the main path. This is an access barrier: the content does not let the learner (or the simulator) confirm the prerequisite state before advancing.

Proposed change

Add an explicit, on-page confirmation step at the end of 07d-confirm-model-access.md (not buried only in the side quest) that has the learner:

  1. State which billing path they chose (organization centralized vs. personal).
  2. Open daily-report-status.lock.yml and visually confirm the permissions.copilot-requests / secret configuration matches that choice.
  3. Recompile, commit, and push if anything doesn't match.
    Add this confirmation as its own checklist item in the Step 7d checkpoint, distinct from the generic "I chose a billing path and completed all configuration steps" line, so it is independently verifiable both by learners and by future content audits.
Failure mode classification

Access barrier (environment/configuration state-tracking gap, not conceptual difficulty).

Quantitative guardrail

Current 07d-confirm-model-access.md rubric: overall_score 6.25/10, active_learning 6.3, checkpoint_quality 0.0, scaffolding 5.0 → learning KPI index = (2.0×6.3 + 2.0×0.0 + 1.5×5.0)/5.5 = 3.65/10. Adding an explicit verification sub-step increases active, hands-on checking (raises active_learning) and strengthens the existing checkpoint without removing any current content, so overall_score and the KPI index should hold flat or rise. No scaffolding or prerequisite content is removed.

Acceptance criteria
  • The shared curriculum quantitative assessment overall_score for 07d-confirm-model-access.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
  • Hands-on practice, checkpoints, and scaffolding are preserved or strengthened (the new verification sub-step is additive, not a replacement for existing guidance)
  • A learner following only 07d-confirm-model-access.md (without re-reading the side quest) can state with certainty which billing path is active and that the lock file matches it, before proceeding to Step 8
Suggested owner

workshop maintainer (content restructuring across two linked files; needs judgment about which checklist wording avoids duplicating the side quest)
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 小时
30 天内合并 PR
17

环境准备

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