Repository navigation
[detection-analysis] Detection Analysis Report — 2026-10-19 #70391
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Detection Analysis Report. A newer discussion is available at Discussion #70656. |
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-10-18T23:21:57Z→2026-10-19T23:21:57Zpartialflag remaining)gh-aw-detection: false): 79 (13.2%)Warning
3 workflows explicitly disable
gh-aw-detectionwhile running more than 3 times in the window (Rule 1). All three are smoke-test workflows (Smoke Copilot,Smoke Copilot SDK Routed,Smoke Pi Routed) with the override hardcoded in their.mdfrontmatter — likely intentional for engine-routing smoke tests, but flagged per the configured threshold since no exception/comment documents the intent. No detection-job-level failures (Rule 2) or flapping configurations (Rule 3) were found.Comparison Chart
Misconfigured Workflows
gh-aw-detection: falseon a high-frequency workflow (Rule 1)gh-aw-detection: falseon a high-frequency workflow (Rule 1)gh-aw-detection: falseon a high-frequency workflow (Rule 1)Example run: §39176941475 (Smoke Copilot)
View All Run Metrics
Top 20 workflows by run count in the window:
236 distinct workflows ran in the window; the remainder were mostly single/low-frequency smoke-test workflows with 1–3 runs each.
View Historical Trend
9 daily snapshots over the last 30 days (cache-memory trending history). Regular-run volume has grown from single digits to 21–79/day over the past week, while detection success rate has fluctuated 76–93%; today's 81.9% sits mid-range.
Recommendations
gh-aw-detection: falseoverride insmoke-copilot.md,smoke-copilot-sdk-routed.md, andsmoke-pi-routed.md— add a short frontmatter comment explaining the smoke-test rationale so future audits don't re-flag it, or re-enable detection if there's no longer a reason to skip it.References:
All reactions