[tools] (Reference Coverage) Add a JSON file to manually override coverage goals #2323
Conversation
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
|
Learn Build status updates of commit 606de23: ✅ Validation status: passed
For more details, please refer to the build report. |
ElizabethSamuel-MSFT
approved these changes
Aug 8, 2025
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.
Based on feedback from @samantharamon.
Methods like this are counted as needing sample coverage for our metrics but shouldn't be. This PR adds a file to manually override any coverage data for a class/interface/enum. The field count exists to serve as a reset: if the field count is different when running the coverage measurement script, the override won't happen. This means that if API are added to the class in question, it will be measured again.