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

[Safe Outputs Conformance] USE-003: 2 handlers disable staged-mode effects without a visible staged-preview marker

Aperta Adatta ai principianti
  • Qualcosa non va?
#71,063 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
70/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions, javascript
Ambito
devtools

Direzione di ricerca

Leggi actions/setup/js/pr_lifecycle.cjs e actions/setup/js/work_queue_claim_scope.cjs, poi cerca logStagedPreviewInfo o generateStagedPreview per trovare la convenzione di output esistente. Aggiungi un indicatore visibile dell’anteprima di staging a entrambi i percorsi di staging, mantenendo il comportamento dell’errore di ambito. Esegui bash scripts/check-safe-outputs-conformance.sh; il lavoro è completo quando USE-003 passa per entrambi i file.

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

Descrizione

automated conformance good-first-issue safe-outputs
Conformance Check Failure

Check ID: USE-003
Severity: LOW (2 occurrences, easy fix)
Category: Usability (Staged Mode Preview Format)

Problem Description

Section on Staged Mode requires handlers that respond to GH_AW_SAFE_OUTPUTS_STAGED to clearly mark their staged behavior, conventionally with a theater-mask (U+1F3AD) emoji in the preview/log output so users scanning run logs can immediately tell an action was suppressed in staged mode. Two handlers check the staged-mode flag but take a silent/exception path instead of emitting a marked preview line:

  • actions/setup/js/pr_lifecycle.cjs (line ~12): if (process.env.GH_AW_SAFE_OUTPUTS_STAGED === "true") return null; — silently short-circuits with no log output at all.
  • actions/setup/js/work_queue_claim_scope.cjs (line ~192): if (process.env.GH_AW_SAFE_OUTPUTS_STAGED === "true" || execution?.staged === true) throw scopeError("read-only Claim preview cannot perform resource effects"); — throws a scope error whose message does not include the staged-preview emoji/marker.
Affected Components
  • actions/setup/js/pr_lifecycle.cjs
  • actions/setup/js/work_queue_claim_scope.cjs
<b>Current vs Expected Behavior</b>
Current Behavior

pr_lifecycle.cjs returns null with no log line, so a user cannot tell from output alone that staged mode suppressed an effect. work_queue_claim_scope.cjs throws a plain-text scopeError without the staged-preview marker, so the error could be mistaken for a genuine failure rather than an expected staged-mode guard.

Expected Behavior

Both paths should emit (or include in their thrown/returned context) a clearly marked staged-mode notice, e.g. logging \ud83c\udfad Staged Mode Preview: skipping PR lifecycle effect (GH_AW_SAFE_OUTPUTS_STAGED) before returning null in pr_lifecycle.cjs, and prefixing the work_queue_claim_scope.cjs scope error message with the same emoji/marker so it is visibly distinguished from a real scope violation.

Remediation Steps
  1. In actions/setup/js/pr_lifecycle.cjs (~line 12), add a core.info or equivalent log line containing the \ud83c\udfad emoji and "Staged Mode Preview" text immediately before the early return null;.
  2. In actions/setup/js/work_queue_claim_scope.cjs (~line 192), prefix the scopeError message passed when staged with the \ud83c\udfad emoji/marker (or log a separate staged-preview notice before throwing), while keeping the thrown error type/behavior unchanged for callers.
  3. Confirm the staged-mode output format matches the pattern used elsewhere in the codebase (search for logStagedPreviewInfo/generateStagedPreview for the established convention) so this is consistent across handlers.
Verification

After remediation, verify the fix by running:

bash scripts/check-safe-outputs-conformance.sh

USE-003 should pass for both listed files.

References
  • Safe Outputs Specification: docs/src/content/docs/specs/safe-outputs-specification.md
  • Conformance Checker: scripts/check-safe-outputs-conformance.sh
  • Run: §39729823556
  • Date: 2026-10-22

Generated by ✅ Daily Safe Outputs Conformance Checker · claude · agent · 132.9 AIC · ⌖ 0.552 AIC · ⊞ 5.4K · ◷

  • expires on Oct 22, 2026, 9:54 PM UTC-08:00
Lingua principale
Go
Stelle
5.4k
Fork
596
Merge medio
3h 41m
PR unite (30g)
829

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 github/gh-aw

Tutte le issue di github/gh-aw

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.