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

[workshop-coverage] Workshop Coverage Status — 2026-10-12

已关闭
  • 哪里不对？
#415 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

The proposed workshop fixes are already in a draft PR, and the issue asks for that PR to be merged; the payload does not name the PR or affected file paths. Start by checking the linked PR and the cited Track 1–3 lab materials, especially Track 3 Lab 6 and Track 2 Lab 2. Done means the proposed content corrections and glossary entries are merged; the attendee-facing decision about azure-rest-api-reference remains open for human guidance.

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

描述

report workshop-coverage

Run: https://github.com/Azure/git-ape/actions/runs/38307437419
Features assessed: 8 agents, 16 skills, 0 core workflows (no refs table populated by inventory this run)
Coverage: 20 / 24 (per inventory grep-proxy; 2 of the 4 "uncovered" signals were false positives, confirmed below)
Gaps found: 6 (2 content-drift bugs, 4 glossary/citation gaps)
Proposed this run: Draft PR — "Fix workshop destroy-lifecycle content drift and close glossary gaps" (closes #392)

Gaps & proposed work
Feature Type Persona / Track Action Status
Track 3 Lab 6 destroy flow (internal contradiction: old per-RG flow vs. stack-based flow) content drift DevOps/SRE / Track 3 Rewrote Step 4 to match the stack-based flow consistently; removed duplicated Step 7 In PR
az group delete anti-pattern in cleanup sections (Track 2 Lab 5, Track 3 Lab 6) content drift Engineer / T2, DevOps / T3 Replaced with /azure-stack-destroy In PR
azure-stack-deploy skill Engineer / T2, DevOps / T3 Glossary entry added (behaviour already lab-covered via @git-ape) In PR
azure-stack-destroy skill Engineer / T2, DevOps / T3 Glossary entry added In PR
azure-requirements-gatherer agent Beginner / T1, Engineer / T2 Glossary entry added — false positive in inventory (covered under display name "Requirements Gatherer" in Track 1/2 labs, deck, demo script) In PR
azure-resource-availability skill Beginner / T1 Named explicitly in Track 1 Lab 2 Step 3 (behaviour already described, skill never named) In PR
azure-rest-api-reference skill Engineer / T2 (tentative) "Going further" citation added in Track 2 Lab 2 — internal correctness tool with no attendee-facing behaviour today, so no dedicated lab section was invented In PR
.github/skills/community/* and git-ape.agent.md (recently changed per inventory) skill/agent N/A No workshop action — out of scope this run (see detail below) in sync (deferred)
Coverage detail
  • Scope filter applied: Dropped no features for being off-topic (Azure/persona scope) this run — all assessed gaps are first-party Git-Ape agents/skills already within the program's Azure focus.
  • azure-requirements-gatherer showed 0 refs by exact slug match in the inventory's coarse grep, but reading Track 1 Lab 2 (lab-02-first-deploy.md), the guided demo script, Track 2 Lab 2, and the Track 2 deck speaker notes confirms it is extensively covered under its display name "Requirements Gatherer." This is a grep-proxy false positive, not a real gap — closed only the glossary omission, no lab content was rewritten.
  • azure-resource-availability: Track 1 Lab 2 Step 3 already fully describes the availability-check behaviour (region, runtime, provider registration, CAF-name uniqueness) but never names the skill. Naming-only fix.
  • azure-rest-api-reference: this is an internal tool the Template Generator agent invokes before writing ARM resource properties — attendees never invoke it directly in any current lab. Rather than inventing a lab section around an internal implementation detail, added a one-line citation in Track 2 Lab 2's "Going further" section. Persona ambiguity flagged for a human: if a future lab wants to make this attendee-facing (e.g., a callout in Lab 3's security-deep-dive error-recovery flow, where an incorrect API version could plausibly cause a real deploy failure), that would be a deliberate scope decision, not something to infer from 0 refs alone.
  • azure-stack-deploy / azure-stack-destroy: both had 0 refs by exact skill-slug match, but their behaviour (the az stack sub create / az stack sub delete --action-on-unmanage deleteAll primitives) is already taught through @git-ape's deploy/destroy flow in Track 2 Lab 2 and Track 3 Lab 6. Rather than invent a new lab, mapped the CLI primitive attendees already see to the skill name that drives it via glossary entries, and used the skill names directly in the corrected destroy-cleanup call sites (see content-drift fixes above).
  • Recently changed feature files per inventory (git-ape.agent.md, .github/skills/community/README.md): git-ape.agent.md's only recent change was a model-version bump (Claude Opus 4.6 → 4.8), which is not attendee-facing content and needs no workshop update. .github/skills/community/README.md documents the community skill registry; workshops reference "community" only in passing marketing copy (deck recap slides, not the registry feature itself) — the actual registry mechanism (.github/skills/git-ape-skills/ repository-backed discovery) does not exist in the current main tree per direct inspection, so there is no live feature to cover yet. Deferred — re-check next run once/if that mechanism lands on main.
  • Prior unresolved run: issue #392 documented the same two content-drift bugs and four glossary gaps, but its companion PR was never opened because GitHub Actions lacked permission to create/approve pull requests in a prior run. The underlying main content was therefore never fixed. This run re-verified every finding against current main (all four were still present) and re-applied the identical fixes in a fresh PR; Closes #392 is included so the backlog item clears on merge.
Recommended next steps
  • Merge the linked draft PR to apply the destroy-lifecycle contradiction fix and close the glossary gaps.
  • Confirm whether Settings → Actions → General → "Allow GitHub Actions to create and approve pull requests" is enabled; issue #392 indicates it previously was not, which is why this run had to resubmit prior work as a new PR.
  • Human decision needed: should azure-rest-api-reference get a dedicated attendee-facing callout in Track 2 Lab 3's security-deep-dive error-recovery flow, or remain citation-only? No action taken pending guidance.
  • Revisit .github/skills/community/* workshop coverage once (if) the repository-backed community skill discovery mechanism (seen referenced in git history as .github/skills/git-ape-skills/) actually lands on main — it is not present in the current tree, so no lab content was written for it this run.

Generated by Workshop Content Auto-Updater · copilot · auto · 140.3 AIC · ⌖ 8.86 AIC · ⊞ 12K · ◷

主要语言
JavaScript
星标
273
派生
49
平均合并
2 天 12 小时
30 天内合并 PR
28

环境准备

在 Codespaces 中打开

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

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

从这里开始

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

Azure/git-ape 的其他 Issue

查看 Azure/git-ape 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

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