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

[workflow-editor] Trim duplicated rule restatement in guidelines-enforcer

Aperta Adatta ai principianti
  • Qualcosa non va?
#3,927 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
75/100
Tipo di issue
Refactoring
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions
Ambito
ci-cd, devops

Direzione di ricerca

Inizia da .github/workflows/guidelines-enforcer.md e confronta il suo passaggio di revisione in schedule-mode con le sezioni autorevoli in .github/workflows/guidelines.md. Fai in modo che l’istruzione di revisione punti a tali sezioni senza ripeterne le regole, quindi esegui gh aw compile --validate per rigenerare e verificare .github/workflows/guidelines-enforcer.lock.yml.

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-enforcer.lock.yml, .github/workflows/guidelines-enforcer.md

What changed

guidelines-enforcer.md's schedule-mode review step re-explained ten
guideline rules with a full sentence of restated logic for each one —
numbered headers, alert callouts, tooling progression, step ordering,
schedule syntax, Codespaces-first design, prerequisite discipline,
checkpoint presence, voice/tone, and environment alternatives. All of
that detail already lives in .github/workflows/guidelines.md, which
this same step already instructs the agent to "read in full" before
reviewing any files.

Why

Restating the rule set inside the prompt is duplicated guidance the
agent doesn't need — it already has the authoritative source loaded.
The bullet list also drifts out of sync with guidelines.md over time
since edits to one don't automatically update the other.

Fix

Replaced the ten-bullet restatement with one short sentence that
points to the specific guidelines.md sections relevant to review
(Header style, Alert callouts, Codespaces-first tooling progression,
Step ordering, Schedule triggers, Core route and environment side
quests, Prerequisite discipline, Checkpoint checklist size limit /
Dispatcher pages, and Learner empathy). This keeps the instruction
Skills-like: short, direct, and pointing learners (and the agent) to
one source of truth instead of repeating it.

Files changed

  • .github/workflows/guidelines-enforcer.md — trimmed the duplicated
    rule list in the "Review each file" step
  • .github/workflows/guidelines-enforcer.lock.yml — regenerated with
    gh aw compile --validate

[!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 · 53.4 AIC · ⌖ 9.2 AIC · ⊞ 7.5K · ◷

  • expires on Sep 29, 2026, 7:53 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 '36393520338' -n agent -D '/tmp/agent-36393520338'

# Resolve the bundle source ref, fetch it into a temporary ref, then create the local branch
bundle_path='/tmp/agent-36393520338/aw-workflow-skills-editor-guidelines-enforcer-trim.bundle'
temp_ref='refs/bundles/create-pr-workflow-skills-editor-guidelines-enforcer-trim-822b32b0a3806277-dc6b7c89'
target_ref='refs/heads/workflow-skills-editor/guidelines-enforcer-trim-822b32b0a3806277'
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-skills-editor/guidelines-enforcer-trim-822b32b0a3806277'
# 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-skills-editor/guidelines-enforcer-trim-822b32b0a3806277'

# Create the pull request
gh pr create --title '[workflow-editor] Trim duplicated rule restatement in guidelines-enforcer' --base 'main' --head 'workflow-skills-editor/guidelines-enforcer-trim-822b32b0a3806277' --repo 'githubnext/gh-aw-workshop'
Lingua principale
JavaScript
Stelle
49
Fork
20
Merge medio
7h 12m
PR unite (30g)
26

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.