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

[workflow-editor] Remove duplicate golden-ticket billing guidance from guidelines.md

Chiusa Adatta ai principianti
  • Qualcosa non va?
#4,139 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à
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
82/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions
Ambito
documentation

Direzione di ricerca

Modifica .github/workflows/guidelines.md, confrontando la dichiarazione dettagliata di Golden-Ticket sotto "Workshop delivery assumptions" con il duplicato sotto "Golden-Ticket Workshop Surfaces". Mantieni la regola dettagliata e sostituisci la ripetizione con un riferimento su una sola riga, quindi valida i sette workflow dipendenti con --validate e conferma che il contenuto di nessun file di lock sia cambiato.

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/guidelines.md

What changed

.github/workflows/guidelines.md stated the golden-ticket org/billing provisioning rule twice, nearly verbatim:

  • "Workshop delivery assumptions" → Org and billing are pre-provisioned.
  • "Golden-Ticket Workshop Surfaces" → Org provisioning and billing are handled by the golden-ticket system.

Both bullets said the provisioning tooling creates the workshop org, assigns Copilot seats, and covers billing, and that core workshop content should not include org/billing setup steps. Keeping both forces every workflow that imports this shared guidelines file to re-read the same instruction twice.

Fix

Kept the detailed statement in "Workshop delivery assumptions" (the first and more complete occurrence) and shortened the "Golden-Ticket Workshop Surfaces" bullet to a one-line summary that points back to it, instead of repeating the full rule.

File changed

  • .github/workflows/guidelines.md (one bullet shortened, no behavior change)

Why this is more Skills-like

GitHub Skills lessons state a rule once and reference it, rather than restating full guidance in multiple sections. This keeps the shared guidelines file leaner for every dependent workflow (guidelines-enforcer, side-quest, security-side-quest, workshop-author, workshop-explanatory-diagrams, workshop-skill-activity-author, workshop-ui-screenshots) that reads it, without losing any guidance — the full rule is still stated once, just not twice.

No lock files needed regeneration: guidelines.md is referenced by path (not inlined) in the dependent workflows, so I validated by recompiling all seven dependent workflows with --validate and confirmed no lock file content changed as a result of this edit.

[!WARNING]

Firewall blocked 1 domain

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

  • registry.npmjs.org

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

network:
  allowed:
    - defaults
    - "registry.npmjs.org"

See Network Configuration for more information.

Generated by ✂️ Workflow Skills Editor · copilot · auto · 54.7 AIC · ⌖ 8.2 AIC · ⊞ 9.5K · ◷

  • expires on Oct 4, 2026, 7:42 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 '37106933547' -n agent -D '/tmp/agent-37106933547'

# Resolve the bundle source ref, fetch it into a temporary ref, then create the local branch
bundle_path='/tmp/agent-37106933547/aw-workflow-editor-dedup-golden-ticket-guidelines.bundle'
temp_ref='refs/bundles/create-pr-workflow-editor-dedup-golden-ticket-guidelines-4f616f84ace678f0-9ac95883'
target_ref='refs/heads/workflow-editor/dedup-golden-ticket-guidelines-4f616f84ace678f0'
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 'workflow-editor/dedup-golden-ticket-guidelines-4f616f84ace678f0'
# 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' 'workflow-editor/dedup-golden-ticket-guidelines-4f616f84ace678f0'

# Create the pull request
gh pr create --title '[workflow-editor] Remove duplicate golden-ticket billing guidance from guidelines.md' --base 'main' --head 'workflow-editor/dedup-golden-ticket-guidelines-4f616f84ace678f0' --repo 'githubnext/gh-aw-workshop'
Lingua principale
JavaScript
Stelle
55
Fork
36
Merge medio
1g 6h
PR unite (30g)
15

Preparare l'ambiente

Apri in Codespaces

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

  • Nessun Dockerfile né file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

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.