[daily-code-metrics] Daily Code Metrics Report - 2026-05-24 #34519
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Daily Code Metrics and Trend Tracking Agent. A newer discussion is available at Discussion #34748. |
Beta Was this translation helpful? Give feedback.
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.
-
Key metrics today: LOC: 1,555,355 | Quality score: 62/100 | Test ratio: 2.06 | Active source files (7d): 1,221
Codebase grew +4.0% in 7 days and +21.6% in 30 days — sustained, fast growth. Test code is keeping pace, but the test-to-source ratio is slowly drifting down (-1.9% / 7d, -5.6% / 30d) as source grows faster than tests. The quality score sits at 62/100, dragged down by code organization (9.8/25) and documentation balance (5/20). Large files (>500 LOC) jumped from 459 → 572 today (+25%), driven by new schema/test fixtures, and have effectively doubled over 30 days.
Workflow churn dominates volume: lock files added +63,158 / deleted -47,300 lines in 7 days across 237 files (excluded from quality score as expected). Source churn is healthy and well-distributed: 441 commits across 1,221 files with a net +42,030 LOC.
📊 Key Visualizations
Quality Score Breakdown
Test coverage and comment density are at full marks. The pressure points are code organization (large files growing faster than the codebase) and documentation balance (code-to-docs ratio is high — codebase is growing faster than docs).
Historical Trends (30 Days)
Total LOC is on a steady upward trajectory; the test ratio is gently sloping down; the quality score has held in the low 60s with mild compression as large files accumulate.
📈 7-Day & 30-Day Trends
🔥 Source Churn (Last 7 Days, excludes
*.lock.yml)Top 10 most active source files
pkg/parser/schemas/main_workflow_schema.jsondocs/public/editor/autocomplete-data.jsonpkg/workflow/gh_cli_permissions_test.goactions/setup/js/send_otlp_span.test.cjspkg/workflow/testdata/wasm_golden/WasmBinary/smoke-copilot.goldenspecs/otel-observability-spec.mdpkg/workflow/observability_otlp_test.gopkg/parser/mcp.gopkg/parser/import_bfs.gopkg/cli/audit_cross_run_render.goGenerated schemas (
main_workflow_schema.json,autocomplete-data.json) and testdata account for the heaviest churn. The OTel/observability work shows up acrosspkg/workflow/observability_otlp_test.go,actions/setup/js/send_otlp_span.test.cjs, andspecs/otel-observability-spec.md.Workflow lock file churn (informational only)
Lock file churn is excluded from the quality score because
*.lock.ymlfiles are generated and would otherwise dominate the signal.💡 Top Recommendations
pkg/parser/schemas/main_workflow_schema.jsonand large*.golden/testdata files — split where humanly authored, accept where generated.pkg/workflowandpkg/parserfeatures.main_workflow_schema.jsonis the rejig docs #1 churned file (12k± lines/week). Consider whether this should live in version control at this granularity or be regenerated on demand.For full per-language and per-directory tables, set
GH_AW_EXPERIMENTS_OUTPUT_FORMAT=full_detail.References:
Report generated by Daily Code Metrics workflow. Historical window: 33 days (2026-04-21 → 2026-05-24). Variant: executive_summary.
Beta Was this translation helpful? Give feedback.
All reactions