Repository navigation
[detection-analysis] Detection Analysis Report — 2026-10-28 #72764
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Detection Analysis Report. A newer discussion is available at Discussion #73057. |
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-27T23:16:39Z→2026-10-28T23:16Zgh-aw-detection: false): 17 (3.7%)Note
No confirmed detection misconfigurations in this window. 131 run records (obsolete-PR / non-execution runs) lacked full
aw_info.json/run_summary.jsondetail and were excluded from detection classification — coverage of those is incomplete by design (metadata-only).Comparison Chart
Misconfigured Workflows
No misconfigured workflows detected in this window.
All 17 "regular" (detection-disabled) runs were single, isolated runs of smoke-test workflows (
Smoke Claude,Smoke Codex,Smoke Copilot*,Smoke Pi*,Smoke OTEL,Smoke Agy (Experimental),Agent Container Smoke Test) plus one occurrence ofDaily GitHub Docs SEO Optimizer. None showed more than 1 run in this 24h window, so rule 1 (gh-aw-detection: falsewith >3 runs/7 days) could not be confirmed from this data — a single 24h snapshot cannot establish a 7-day run-count threshold, and projecting from one observed run would be speculative. No workflow'sdetectionjob itself failed (rule 2), and no workflow alternated between enabled/disabled within the window (rule 3).Engine/workflow mix
No
detection-job failures were observed across 439 runs that had a detection job present injob_details(424success, 15skippedfor detection-disabled runs).View All Run Metrics
Top workflows by run count in the window (176 distinct workflows total; showing top 20 plus all 17 regular/detection-disabled workflows):
View Historical Trend
30 days of history now available (18 of 30 days have data; gaps are left as breaks, not interpolated).
Recommendations
PR Sous Chef(114 runs, 40.4% success) and general failure volume (108 of 440 detection-enabled runs failing) rather than detection itself; worth a separate look atPR Sous Chef's failure pattern if not already tracked.gh-aw-detection: false+ >3-runs rule needs a 7-day log fetch, which is out of scope for a 24h window — consider running this check on a longer cadence (e.g., weekly) if that misconfiguration pattern is a priority.References:
PR Sous Cheffailure example (safe_outputs/"Process Safe Outputs" step)Daily Caveman Optimizerfailure exampleSmoke Agy (Experimental)run (regular/detection-disabled)All reactions