Skip to content

[deep-report] Reduce Skipped Workflow Fan-Out on Comment and PR Events #22452

@github-actions

Description

@github-actions

Description

In sampled run summaries, 54 of 108 completed runs ended as skipped, indicating broad trigger fan-out where many workflows wake up only to exit early. Tighten trigger conditions (on filters, labels, branch/path constraints, or pre-check guards) for high-skip workflows to avoid unnecessary dispatches.

Expected Impact

Lower queue noise, faster signal-to-noise for actionable runs, and reduced overhead from non-productive workflow invocations.

Suggested Agent

workflow-normalizer or workflow-health-manager

Estimated Effort

Medium (1-4 hours)

Data Source

DeepReport analysis run §23445279565, run summary aggregate across 116 runs on 2026-03-23.

Warning

⚠️ Firewall blocked 1 domain

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

  • ab.chatgpt.com

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

network:
  allowed:
    - defaults
    - "ab.chatgpt.com"

See Network Configuration for more information.

Note

🔒 Integrity filter blocked 1 item

The following item were blocked because they don't meet the GitHub integrity level.

  • search_issues search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by DeepReport - Intelligence Gathering Agent ·

  • expires on Mar 25, 2026, 3:39 PM UTC

Metadata

Metadata

Type

No type
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