[detection-analysis] Detection Analysis Report — 2026-08-30 #57261
Replies: 1 comment
|
🤖 Smoke test bot checking in on this Detection Analysis discussion! Everything looks in order here — carry on with the great analysis work. 🎉 Warning Firewall blocked 6 domainsThe following domains were blocked by the firewall during workflow execution:
To allow these domains, add them to the network:
allowed:
- defaults
- "accounts.google.com"
- "android.clients.google.com"
- "clients2.google.com"
- "contentautofill.googleapis.com"
- "www.google.com"
- "www.gstatic.com"See Network Configuration for more information.
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
2026-08-29T23:41:03Z→2026-08-30T23:41:03Zgh-aw-detection: false): 3 (0.7%)Warning
3 workflows explicitly disable the
gh-aw-detectionfeature while running frequently enough (>3 runs in the last 7 days) that detection would meaningfully help catch anomalies. No detection-job-level failures or flag-alternation issues were found.Comparison Chart
Detection-enabled runs vastly outnumber regular runs (403 vs 3) — the run-count panel uses a log scale to keep the "Regular" bar visible. Detection-enabled runs also show a higher success rate (87.6% vs 66.7%) and consume ~6x more tokens on average (129.9k vs 21.0k), consistent with the extra detection-analysis step running as part of those workflows.
Misconfigured Workflows
gh-aw-detection: falseon a high-frequency workflow (>3 runs/7d)gh-aw-detection: falseoverride (or justify it in a comment) so detection runs by default and can catch anomalous smoke-test behavior.gh-aw-detection: falseon a high-frequency workflow (>3 runs/7d)gh-aw-detection: falseon a high-frequency workflow (>3 runs/7d)Example runs (24h window): §33287374932 (Smoke Codex), §33288730255 (Smoke Copilot), §33293189773 (Daily GitHub Docs SEO Optimizer).
No workflows were found with a failing
detectionjob conclusion (rule 2), and no workflow alternated between detection-enabled and detection-disabled within the window (rule 3).View All Run Metrics
Workflows with ≥2 runs in the window (20 of 130 distinct workflows; the remaining 110 each had exactly 1 run):
"Enabled (default)" =
gh-aw-detectionkey absent fromaw_info.json(the feature default). "Enabled (explicit)" = key present andtrue. "Disabled" = key present andfalse.Aggregate metrics:
View Historical Trend
Insufficient history for a trend chart — the cache-memory trending store (
trending/detection-metrics/history.jsonl) has 5 daily entries after today's append; a 30-day trend chart is generated once ≥7 entries exist.Recent daily snapshots:
Today is the first day this window's rules flagged any misconfigured workflows — worth watching whether Smoke Codex / Smoke Copilot / Daily GitHub Docs SEO Optimizer keep the
gh-aw-detection: falseoverride going forward.Recommendations
gh-aw-detectionon Smoke Codex, Smoke Copilot, and Daily GitHub Docs SEO Optimizer — all three run frequently (8-21 times/week) with the feature explicitly off, forgoing anomaly detection on a meaningful share of CI volume.References:
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
api.anthropic.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
All reactions