Skip to content

[deep-report] Tune Daily Code Metrics churn score to ignore generated *.lock.yml files #13741

@github-actions

Description

@github-actions

Description

Daily Code Metrics shows churn stability at 0 because workflow lock files dominate the change set (2,035 files modified in 7 days, with the top churners all being .lock.yml). This inflates churn noise and masks real source-code volatility. Update the churn calculation to exclude generated lock files (or report them separately) so stability reflects actionable change. Reference: Daily Code Metrics Report - 2026-02-04 (Discussion #13699).

Expected Impact

  • More accurate churn stability score
  • Separate visibility into generated workflow churn vs. code churn
  • Better signal for maintainers when stability genuinely changes

Suggested Agent

Code Metrics / Observability agent

Estimated Effort

Quick (< 1 hour)

Data Source

DeepReport Intelligence Briefing - 2026-02-04

AI generated by DeepReport - Intelligence Gathering Agent

  • expires on Feb 6, 2026, 3:26 PM UTC

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions