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

[workflow-editor] Fix broken heading references to shared snippet-validation procedure

Chiusa Adatta ai principianti
  • Qualcosa non va?
#3,771 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
1/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
85/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Ambito
documentation

Direzione di ricerca

Il problema riguarda la correzione di riferimenti a intestazioni errati in tre file markdown: .github/workflows/side-quest.md, security-side-quest.md e workshop-skill-activity-author.md. Attualmente puntano a '### 5. Validate agentic workflow snippets' in workshop-author.md, ma l'intestazione corretta è '### Validate agentic workflow snippets'. Apri ogni file, trova il riferimento e aggiornalo in modo che corrisponda all'intestazione effettiva. Dopo la modifica, esegui 'gh aw compile --validate' per rigenerare i file .lock.yml corrispondenti. Verifica le modifiche controllando che i collegamenti si risolvano correttamente.

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

Descrizione

agentic-workflows documentation workflow-editor

[!CAUTION]
Protected files were modified in this change.
This pull request is in request_review mode and requires explicit human scrutiny before merge.

Protected files: .github/workflows/security-side-quest.lock.yml, .github/workflows/security-side-quest.md, .github/workflows/side-quest.lock.yml, .github/workflows/side-quest.md, .github/workflows/workshop-skill-activity-author.lock.yml, .github/workflows/workshop-skill-activity-author.md

Removes a small piece of broken duplication: three workflow files
(side-quest.md, security-side-quest.md,
workshop-skill-activity-author.md) each pointed learners/agents to a
shared procedure at ### 5. Validate agentic workflow snippets inside
workshop-author.md — but that section is titled ### Validate agentic workflow snippets (no number prefix, and it isn't the fifth heading in
the file). The stale numbered reference was likely left over from an
earlier version of workshop-author.md that has since been reorganized.

Files changed

  • .github/workflows/side-quest.md
  • .github/workflows/security-side-quest.md
  • .github/workflows/workshop-skill-activity-author.md
  • Regenerated .lock.yml files for all three via gh aw compile --validate

Why this is more Skills-like

The fix keeps the "shared procedure" cross-reference pattern (short,
DRY, one canonical source of truth in workshop-author.md) but makes
the pointer actually resolve, so an agent or learner following the link
lands on the right section instead of a numbered heading that doesn't
exist. No behavior, trigger, permission, or safe-output changes — this
is a pure accuracy fix to existing shared guidance text.

[!WARNING]

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

  • api.github.com

[!TIP]
api.github.com is blocked because GitHub API access uses the built-in GitHub tools by default. Instead of adding api.github.com to network.allowed, use tools.github.mode: gh-proxy for direct pre-authenticated GitHub CLI access without requiring network access to api.github.com:

tools:
  github:
    mode: gh-proxy

See GitHub Tools for more information on gh-proxy mode.

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "api.github.com"

See Network Configuration for more information.

Generated by ✂️ Workflow Skills Editor · copilot · auto · 38.6 AIC · ⌖ 8.71 AIC · ⊞ 7.5K · ◷

  • expires on Sep 25, 2026, 7:38 AM UTC

[!NOTE]
This was originally intended as a pull request, but the git push operation failed.

Original error: The process '/usr/bin/git' failed with exit code 1

Workflow Run: View run details and download bundle artifact

The bundle file is available in the agent artifact in the workflow run linked above.

Create the pull request manually 
# Download the artifact from the workflow run
gh run download '35970180586' -n agent -D '/tmp/agent-35970180586'

# Resolve the bundle source ref, fetch it into a temporary ref, then create the local branch
bundle_path='/tmp/agent-35970180586/aw-fix-workshop-author-snippet-heading-ref.bundle'
temp_ref='refs/bundles/create-pr-fix-workshop-author-snippet-heading-ref-14d0d19d5332017c-bd2a05ad'
target_ref='refs/heads/fix/workshop-author-snippet-heading-ref-14d0d19d5332017c'
bundle_source_ref=$(git bundle list-heads "$bundle_path" | awk '$2 ~ /^refs\/heads\// { print $2 }')
if [ -z "$bundle_source_ref" ]; then
  bundle_source_ref=$(git bundle list-heads "$bundle_path" | awk '$2 == "HEAD" { print $2 }')
fi
if [ "$(printf '%s\n' "$bundle_source_ref" | sed '/^$/d' | wc -l | tr -d ' ')" != "1" ]; then
  echo "Expected exactly one bundle source ref, found: $bundle_source_ref" >&2
  exit 1
fi
git fetch "$bundle_path" "${bundle_source_ref}:${temp_ref}"
git update-ref "$target_ref" "$temp_ref"
git checkout 'fix/workshop-author-snippet-heading-ref-14d0d19d5332017c'
# Ensure the working tree matches the updated branch
git reset --hard
# Remove the temporary bundle ref
git update-ref -d "$temp_ref"

# Push the branch to the target remote
git push 'origin' 'fix/workshop-author-snippet-heading-ref-14d0d19d5332017c'

# Create the pull request
gh pr create --title '[workflow-editor] Fix broken heading references to shared snippet-validation procedure' --base 'main' --head 'fix/workshop-author-snippet-heading-ref-14d0d19d5332017c' --repo 'githubnext/gh-aw-workshop'
Lingua principale
JavaScript
Stelle
49
Fork
20
Merge medio
7h 55m
PR unite (30g)
30

Preparare l'ambiente

Non abbiamo ancora controllato i file di configurazione di questo progetto. Parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 githubnext/gh-aw-workshop

Tutte le issue di githubnext/gh-aw-workshop

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.