Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#454 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
55/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github-actions, javascript
Ambito
documentation

Direzione di ricerca

Start by reviewing the workshop labs and the referenced Deployment Stacks, availability-check, and REST API skills to identify where the recommended sections belong. The issue says no lab changes were made because the source behavior was not reviewed deeply, so verify those sources before drafting. Done means adding accurate Track 3 deploy/destroy and Track 2 availability and REST API sections, then comparing them with the skills.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

report workshop-coverage

Run: https://github.com/Azure/git-ape/actions/runs/40399770825
Features assessed: 8 agents, 16 skills, 0 workflows (inventory table empty)
Coverage: 19 / 24 by grep proxy · Gaps found: 8 by name (glossary now covers them)
Proposed this run: draft PR (glossary refresh)

Gaps & proposed work
Feature Type Persona / Track Action Status
azure-requirements-gatherer, azure-template-generator, azure-resource-deployer agent All / glossary Glossary entries In PR
azure-resource-availability, azure-rest-api-reference skill Engineer / T2 Glossary now; lab section recommended Partly in PR
azure-stack-deploy, azure-stack-destroy skill Platform / T3 Glossary now; lab section recommended Partly in PR
git-ape-skills skill Engineer / T2 Glossary now (recently changed) In PR
git-ape agent agent All Changed 2026-10-14; not reviewed in depth deferred
Coverage detail
  • Persona ambiguity: stack deploy/destroy fit Track 3 (CI parity) but could also fit Track 2 hands-on; recommending Track 3.
  • Scope was kept minimal this run: no lab changes were made, to avoid inventing behaviour without reviewing sources deeply.
  • Open workshop-sync issues could not be read (filtered by integrity policy).
Recommended next steps
  • Add a Track 3 lab section on Deployment Stacks deploy/destroy.
  • Add a Track 2 section on availability checks and REST API reference.
  • Review git-ape.agent.md changes (2026-10-14) against labs.

Generated by Workshop Content Auto-Updater · copilot · auto · 22 AIC · ⌖ 1.01 AIC · ⊞ 5.2K · ◷

Lingua principale
JavaScript
Stelle
279
Fork
49
Merge medio
1g 23h
PR unite (30g)
26

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Azure/git-ape

Tutte le issue di Azure/git-ape

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.