Repository navigation
[detection-analysis] Detection Analysis Report — 2026-10-22 #71243
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Detection Analysis Report. A newer discussion is available at Discussion #71510. |
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-detectionfeature detail downloaded, so that slice is not included belowgh-aw-detection: false): 6 (1.4%)Note
No misconfigured workflows were detected in the analyzed window. All 6 "regular" runs belong to experimental/smoke-test workflows (
Smoke Pi Routed,Engine Conformance Agy,Engine Conformance Aider,Smoke Copilot SDK Routed,Daily GitHub Docs SEO Optimizer) with ≤3 runs each — none crossed the >3-runs-in-7-days threshold for rule 1, nodetectionjob showed a failing conclusion (rule 2, checked across 413 runs where adetectionjob actually executed), and no workflow alternated between enabled/disabled within the window (rule 3).Comparison Chart
Caveat: the regular-run sample (n=6) is too small for a statistically meaningful success-rate or token comparison — it's dominated by a couple of intentionally-failing engine-conformance smoke tests (
Engine Conformance Agy,Engine Conformance Aider), and the large token gap mostly reflects a few high-volume detection-enabled production workflows (e.g.Metrics Collector,Daily Go Test Parallelizer,Avenger) rather than detection overhead itself.Misconfigured Workflows
No misconfigured workflows detected in this window.
View All Run Metrics (top 25 of 167 workflows by run count)
...and 142 additional workflows with 1 run each in this window (omitted for brevity).
View Historical Trend
23 days of history now exist in cache-memory; the chart above plots the available 30-day window (12 days with actual data, gaps shown for missing days).
Recommendations
gh-aw-detectionfeature is enabled by default across the fleet (98.6% of runs) and no workflow shows a failingdetectionjob or inconsistent opt-out behavior.features.gh-aw-detectiondetail. Consider raisingmax_storage/countfor this report's log pre-fetch, or splitting it across two smaller windows, if full 24h coverage is required going forward.gh-aw-detection: falseis intentional for the 5 smoke/conformance workflows currently using it, consider documenting that opt-out directly in each workflow's frontmatter comment so future audits don't need to re-derive the rationale.References:
All reactions