[workflow-style] Normalize report formatting for non-compliant workflows

Aperta Adatta ai principianti
  • Qualcosa non va?
#77,449 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
62/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github-actions, markdown
Ambito
devtools, documentation

Direzione di ricerca

Inizia dai due prompt di workflow indicati, .github/workflows/daily-astrostylelite-markdown-spellcheck.md e .github/workflows/daily-compiler-threat-spec-optimizer.md, e individua le loro sezioni di indicazioni sull'output. Usa daily-repo-chronicle.md, audit-workflows.md e la skill di reporting condivisa come schema di riferimento. È completato quando ciascun prompt richiede esplicitamente titoli di livello h3 o inferiore, blocchi details comprimibili per le prove lunghe e l'ordine panoramica, metriche/issue, prove, prossime azioni.

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

Descrizione

cookie
Overview

The last-24-hour workflow-style review found two active reporting workflows whose report instructions do not explicitly establish all three project conventions: h3-or-lower headings, progressive disclosure with <details>, and a clear overview → key metrics/issues → detailed evidence → next actions structure.

Review scope
  • Workflows reviewed: 36 active reporting/documentation workflows
  • Valid run metadata pairs: 290
  • Skipped malformed or incomplete run directories: 181
  • Non-compliant workflows: 2
  • Duplicate checks: no visible matching open issue or unmerged Copilot PR was returned; the GitHub integration filtered parts of the search response and rejected unsupported PR search fields/qualifiers
Non-compliant workflows and required changes
Workflow Findings Required change
.github/workflows/daily-astrostylelite-markdown-spellcheck.md The output guidance shows a collapsible details example, but does not explicitly require h3-or-lower report headings or define a consistent report structure. Add explicit h3+ heading guidance; require long findings/details to use <details><summary><b>...</b></summary>...</details>; define overview → key metrics/issues → detailed findings → next actions.
.github/workflows/daily-compiler-threat-spec-optimizer.md The output guidance asks for collapsible content but does not explicitly require h3-or-lower report headings or define the report sequence. Add explicit h3+ heading guidance; require progressive disclosure for long evidence; define the same visible-summary and collapsible-detail structure.
Recommended format

Use a concise visible summary followed by collapsible evidence:

Detailed findings

Long tables, raw logs, and per-item evidence belong here.

Good references

Use .github/workflows/daily-repo-chronicle.md, .github/workflows/audit-workflows.md, and the shared reporting skill as reference patterns. Keep critical decisions visible, use - [ ] for follow-up actions, and include workflow run references as [§12345](https://github.com/owner/repo/actions/runs/12345) where applicable.

Acceptance criteria
  • Both workflows explicitly require h3-or-lower headings in generated reports.
  • Both workflows specify <details> progressive disclosure for long content.
  • Both workflows specify the overview → key metrics/issues → detailed evidence → next actions order.
  • The next review reports both workflows as compliant.

Generated by 🔧 Workflow Normalizer · codex · gpt56 · ~5 AIC · ⌖ ~1 AIC · ⊞ 15.5K · ◷

  • expires on Nov 14, 2026, 4:56 AM UTC-08:00
Lingua principale
Go
Stelle
5.6k
Fork
625
Merge medio
5h 42m
PR unite (30g)
796

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.