Exclude actions-lock.json from daily code metrics churn report#40532
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Exclude code-generated files from daily metrics report
Exclude actions-lock.json from daily code metrics churn report
Jun 21, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Daily Code Metrics workflow spec to treat actions-lock.json as a generated artifact (similar to *.lock.yml) so churn-derived metrics and the “Most Active Source Files” report aren’t polluted by automated lock/cache updates.
Changes:
- Expanded churn exclusions to cover both
*.lock.ymlandactions-lock.json(instructions, churn stability command, chart spec, and report captions). - Renamed “Workflow Lock File Churn” to “Generated File Churn” and updated related report wording.
- Updated the churn data-storage note to describe the source vs generated-file split including
actions-lock.json.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/daily-code-metrics.md |
Updates churn exclusion rules, reporting language, and churn-stability guidance to ignore actions-lock.json alongside *.lock.yml. |
.github/workflows/daily-code-metrics.lock.yml |
Regenerated compiled workflow lock to reflect the markdown workflow changes. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 2
| ``` | ||
|
|
||
| **Note**: Churn metrics are split into `source` (excludes `*.lock.yml`) and `lock_files` (only `*.lock.yml`) for separate tracking. | ||
| **Note**: Churn metrics are split into `source` (excludes `*.lock.yml` and `actions-lock.json`) and `generated_files` (only `*.lock.yml` and `actions-lock.json`) for separate tracking. |
| - **Net Change**: +/-X,XXX lines | ||
|
|
||
| **Note**: Lock file churn is reported separately and excluded from quality score calculations to avoid noise from generated files. | ||
| **Note**: Generated file churn (`.lock.yml` and `actions-lock.json`) is reported separately and excluded from quality score calculations to avoid noise from code-generated files. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
actions-lock.jsonis a code-generated file (like*.lock.yml) but was not excluded from churn calculations, polluting "Most Active Source Files" and inflating the Churn Stability quality score component.Changes
actions-lock.jsonto all exclusion rules alongside*.lock.yml: churn section instructions, Churn Stability git command, and Code Churn chart spec:!*.lock.yml ':!**/actions-lock.json'sourcevs generated-file split description to name both exclusions