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

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

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

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Review the workshop labs named in the issue, especially Track 3 Lab 6 and Track 2 Labs 2 and 5, then compare the proposed fixes with the current content and the open PRs from issues #392, #414, and #415. The issue says a draft PR already contains overlapping changes, so check its diff before taking anything on; done means the destroy flow is consistent and the listed glossary and skill coverage gaps are addressed without duplicating another PR.

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

描述

report workshop-coverage workshop-sync

Run: https://github.com/Azure/git-ape/actions/runs/39323030425
Features assessed: 8 agents, 16 skills, 0 core workflows (no refs table populated by inventory this run)
Coverage: 21 / 24 (per inventory grep-proxy; 2 of the "uncovered" signals were false positives on closer reading; git-ape-skills was a genuine new gap)
Gaps found: 7 (2 content-drift bugs, 5 glossary/citation/pointer gaps)
Proposed this run: Draft PR — "Fix destroy-lifecycle content drift and close workshop glossary/skill gaps"

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 Merged into one consistent stack-based narrative; removed duplicated steps 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 + explanatory callout 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 (covered under display name "Requirements Gatherer") 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 In PR
git-ape-skills (community skill discovery/install) skill DevOps/SRE / T3 New gap, newly landed on main 2026-10-09. Glossary entry + grounded pointer in Track 3 Lab 6's existing "Explore more skills" next-step In PR
.github/skills/community/* registry docs docs N/A No dedicated workshop action — mechanism is the git-ape-skills skill itself, now covered above in sync
Coverage detail
  • Scope filter applied: No features were dropped for being off-topic this run — all assessed gaps are first-party Git-Ape agents/skills already within the program's Azure focus. No aws-* or equivalent out-of-scope skills were present in this inventory.
  • azure-requirements-gatherer: 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." Grep-proxy false positive — closed only the glossary omission, no lab content 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 named the skill. Naming-only fix.
  • azure-rest-api-reference: internal tool the Template Generator agent invokes before writing ARM resource properties — attendees never invoke it directly in any current lab. Added a one-line citation in Track 2 Lab 2's "Going further" section rather than inventing a lab around an internal implementation detail. Persona ambiguity flagged for a human: a future lab could 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 is a deliberate scope decision, not inferred from 0 refs alone.
  • azure-stack-deploy / azure-stack-destroy: both had 0 refs by exact skill-slug match, but their behaviour (az stack sub create / az stack sub delete --action-on-unmanage deleteAll) is already taught through @git-ape's deploy/destroy flow in Track 2 Lab 2 and Track 3 Lab 6. 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.
  • git-ape-skills (genuinely new this run): landed on main 2026-10-09 (.github/skills/git-ape-skills/SKILL.md — repository-backed community skill discovery/install). A prior coverage run (#415) deferred this exact mechanism because it "does not exist in the current main tree per direct inspection" — it now does. Verified directly against the SKILL.md source: search is read-only against a bundled registry; install requires explicit per-skill approval, a pinned commit SHA, and only ever installs from Azure/git-ape. Grounded the workshop mention in Track 3 Lab 6's pre-existing "Explore more skills" bullet (the natural attendee touchpoint at program wrap-up) plus a glossary entry — did not invent a dedicated lab since the feature is a thin discovery/install utility, not a deployment workflow with enough surface area to justify 10-20 minutes of lab time.
  • Prior unresolved content drift (previously reported in issues #392/#414/#415): the destroy-lifecycle contradiction and az group delete anti-pattern were still live on main as of this run (both older PRs are open but unmerged) — re-verified against current lab content before re-applying the same fixes in this PR.
Recommended next steps
  • Merge the linked draft PR to apply the destroy-lifecycle contradiction fix and close the glossary/skill gaps.
  • Reconcile with the still-open PRs from issues #392/#414: this run's PR covers the same two content-drift bugs (re-verified fresh against current main) plus the new git-ape-skills coverage those earlier runs could not include. A human should pick one PR to merge and close the others to avoid duplicate/conflicting diffs.
  • 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.
  • No action needed on .github/skills/community/* — the registry mechanism is now the same thing as git-ape-skills, covered above.

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

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

环境准备

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