Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#454 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions, javascript
Área
documentation

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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 · ◷

Lenguaje dominante
JavaScript
Estrellas
279
Forks
49
Merge medio
1 d 23 h
PR fusionados (30 d)
26

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Azure/git-ape

Todos los issues de Azure/git-ape

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.