Skip to content

[deep-report] Add gh-aw-detection: true to 8 audit/report/detector-named scheduled workflows #52311

Description

@github-actions

Description

The Detection Analysis Report (#52181) flagged 8 scheduled workflows whose names match audit/report/detector/analyzer keywords but are missing gh-aw-detection: true in their frontmatter, so their AI-credit usage is not captured by the detection pipeline like their peers:

  • .github/workflows/daily-action-setup-security-audit.md
  • .github/workflows/daily-firewall-report.md
  • .github/workflows/daily-regression-audit-kiro.md
  • .github/workflows/daily-schema-audit-cursor.md
  • .github/workflows/daily-sentrux-report.md
  • .github/workflows/designer-drift-audit.md
  • .github/workflows/go-pattern-detector.md
  • .github/workflows/static-analysis-report.md

Verified directly: all 8 files exist and currently contain zero occurrences of gh-aw-detection.

Expected Impact

Closes a monitoring/detection-coverage gap so these 8 daily/weekday-scheduled workflows' AI-credit usage is tracked consistently with the rest of the fleet.

Suggested Agent

General automation/config agent — add gh-aw-detection: true to each workflow's frontmatter and recompile (gh aw compile) to regenerate the corresponding .lock.yml files.

Estimated Effort

Quick (< 1 hour)

Data Source

DeepReport Intelligence Briefing 2026-08-12, mined from Detection Analysis Report #52181.

Generated by 🔬 Deep Report · agent · 198.4 AIC · ⌖ 54.5 AIC · ⊞ 11.4K ·

  • expires on Aug 14, 2026, 7:07 AM UTC-08:00

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions