Skip to content

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

Description

@github-actions

Overview

Daily style normalization scan identified 65 non-compliant reporting workflows out of 79 reviewed.
These workflows contain #/## header instructions or examples — violating the project guideline that report headers must start at ### — and/or lack progressive disclosure (<details>) guidance.

Good reference examples: daily-repo-chronicle, audit-workflows, daily-safe-outputs-conformance.


Style Issues Found

Workflow Issues
agentic-token-audit h1/h2 in examples, h1/h2 in body text
agentic-token-trend-audit h1/h2 in examples, h1/h2 in body text
api-consumption-report h1/h2 in examples, h1/h2 in body text
artifacts-summary h1/h2 in examples
audit-workflows h1/h2 in body text
copilot-pr-merged-report h1/h2 in examples, h1/h2 in body text
daily-agentrx-trace-optimizer h1/h2 in examples, h1/h2 in body text
daily-ambient-context-optimizer h1/h2 in body text
daily-astrostylelite-markdown-spellcheck h1/h2 in body text
daily-aw-cross-repo-compile-check h1/h2 in examples, h1/h2 in body text
daily-awf-spec-compiler-surfacing h1/h2 in body text
daily-cache-strategy-analyzer h1/h2 in examples, h1/h2 in body text
daily-caveman-optimizer h1/h2 in examples, h1/h2 in body text
daily-choice-test h1/h2 in body text
daily-cli-performance h1/h2 in examples, h1/h2 in body text
daily-code-metrics h1/h2 in examples, h1/h2 in body text
daily-community-attribution h1/h2 in examples, h1/h2 in body text
daily-compiler-quality h1/h2 in examples, h1/h2 in body text
daily-compiler-threat-spec-optimizer h1/h2 in body text
daily-doc-healer h1/h2 in examples, h1/h2 in body text
daily-doc-updater h1/h2 in body text
daily-experiment-report h1/h2 in examples, h1/h2 in body text
daily-file-diet h1/h2 in examples, h1/h2 in body text
daily-firewall-report h1/h2 in examples, h1/h2 in body text
daily-formal-spec-verifier h1/h2 in examples, h1/h2 in body text
daily-function-namer h1/h2 in examples, h1/h2 in body text
daily-geo-optimizer h1/h2 in examples, h1/h2 in body text
daily-hippo-learn h1/h2 in body text
daily-issues-report h1/h2 in examples, h1/h2 in body text
daily-malicious-code-scan h1/h2 in examples, h1/h2 in body text
daily-mcp-concurrency-analysis h1/h2 in examples, h1/h2 in body text
daily-model-inventory h1/h2 in examples, h1/h2 in body text
daily-model-resolution h1/h2 in examples, h1/h2 in body text
daily-multi-device-docs-tester h1/h2 in examples, h1/h2 in body text
daily-news h1/h2 in body text
daily-observability-report h1/h2 in examples, h1/h2 in body text
daily-performance-summary h1/h2 in examples, h1/h2 in body text
daily-regulatory h1/h2 in examples, h1/h2 in body text
daily-reliability-review h1/h2 in body text
daily-rendering-scripts-verifier h1/h2 in examples, h1/h2 in body text
daily-repo-chronicle h1/h2 in body text
daily-safe-output-integrator h1/h2 in body text
daily-safe-output-optimizer h1/h2 in body text
daily-safe-outputs-conformance h1/h2 in examples, h1/h2 in body text
daily-safeoutputs-git-simulator h1/h2 in examples, h1/h2 in body text
daily-secrets-analysis h1/h2 in examples, h1/h2 in body text
daily-security-observability h1/h2 in examples, h1/h2 in body text
daily-sentrux-report h1/h2 in body text
daily-skill-optimizer h1/h2 in body text
daily-spdd-spec-planner h1/h2 in body text
daily-syntax-error-quality h1/h2 in examples, h1/h2 in body text
daily-team-evolution-insights h1/h2 in examples, h1/h2 in body text
daily-team-status h1/h2 in body text
daily-testify-uber-super-expert h1/h2 in body text
daily-token-consumption-report h1/h2 in body text
daily-workflow-updater h1/h2 in examples, h1/h2 in body text
daily-yamllint-fixer h1/h2 in examples, h1/h2 in body text
detection-analysis-report h1/h2 in body text
github-mcp-tools-report h1/h2 in examples, h1/h2 in body text
org-health-report h1/h2 in examples, h1/h2 in body text
static-analysis-report h1/h2 in examples, h1/h2 in body text
weekly-blog-post-writer h1/h2 in examples, h1/h2 in body text
weekly-editors-health-check h1/h2 in body text
weekly-issue-summary h1/h2 in body text
weekly-safe-outputs-spec-review h1/h2 in body text

Required Changes Per Workflow

Each non-compliant workflow needs one or more of:

  1. Header level — replace #/## with ###/#### in output format examples and instruction text.
  2. Progressive disclosure — add <details><summary><b>...</b></summary> wrapping for long content sections in the output format instructions.
  3. Report structure — ensure instructions follow: overview → key metrics → collapsible detail → next actions.

Example Fix (Progressive Disclosure)

Before:

## Full Details
- item 1
- item 2
...

After:

### Summary
Key finding here.

<details>
<summary><b>Full Details</b></summary>

- item 1
- item 2
...

</details>

Next Steps

  • Update header levels (#/#####/####) in output format examples
  • Add <details> progressive disclosure to workflows with long report sections
  • Verify updated workflows follow: overview → metrics → collapsible detail → next actions
  • Reference daily-repo-chronicle as a model for compliant structure

Compliance Summary

  • Compliant: 14 workflows
  • ⚠️ Needs Improvement: 65 workflows
  • 📋 Total Reviewed: 79 reporting workflows

Warning

Firewall blocked 1 domain

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

  • awmgmcpg

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

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by 🔧 Workflow Normalizer · 36.8 AIC · ⌖ 7.37 AIC · ⊞ 5.6K ·

  • expires on Jul 7, 2026, 6:09 AM UTC-08:00

Metadata

Metadata

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions