Repository navigation
[detection-analysis] Detection Analysis Report — 2026-11-05 (24h) #75254
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Detection Analysis Report. A newer discussion is available at Discussion #75497. |
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
gh-aw-detection: false): 55 (11.0%)Warning
1 workflow showed a detection-job failure in this window (isolated flake, see below). No systemic
gh-aw-detectionmisconfigurations were found.Comparison Chart
Detection-enabled runs show a higher success rate (+4.7 pts) but ~2.8x the average token usage, consistent with the extra detection pass running on top of the agent job for those workflows. The gap is driven partly by a handful of very token-heavy workflows (e.g.
Daily Go Test Parallelizer,Ponytail Reviewer) that all run with detection enabled.Misconfigured Workflows
detectionjob's "Install GitHub Copilot CLI" step failed once (§42055218246) while 20 other recent runs of this workflow succeeded with detection passing. Monitor for recurrence rather than treating as a lasting misconfiguration; no frontmatter change needed at this time.No workflows were flagged for frequently-disabled detection (
gh-aw-detection: falseon a workflow with >3 runs) — the only runs with detection explicitly disabled were one-off "Smoke" test workflows (20 distinct smoke workflows, 1 run each). No workflows alternated between detection-enabled and detection-disabled within the window.View All Run Metrics
227 distinct workflows ran in the window. Top 25 by run count:
(Remaining 202 workflows each had 1 run; mostly additional one-off "Smoke" tests with detection disabled.)
Metadata-only runs excluded: 283 run directories in the window had only minimal
run.jsonmetadata (noaw_info.json/run_summary.json— consistent with superseded/obsolete PR-triggered runs cancelled by a newer commit). These could not be classified by detection status and are excluded from the counts above.View Historical Trend
36 distinct days of history now recorded (with some gaps in the last 30 days). Detection-run volume has grown sharply over the period while regular-run volume stays consistently low (under ~80/day), reflecting that detection is the default and only a small number of one-off smoke tests opt out.
Recommendations
gh-aw-detectionusage across the fleet is healthy (89% of runs use the default, remaining 11% are intentional one-off smoke tests).PR Code Quality Reviewer'sdetectionjob; if the "Install GitHub Copilot CLI" step fails again on a future run, treat it as a recurring infra issue (e.g. flaky npm registry/network) rather than a one-off.References:
All reactions