chore: re-enable correct coverage reporting #1689
Merged
Conversation
This file contains 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
danielbate
requested review from
digorithm,
arboleya,
Torres-ssf,
Dhaiwat10 and
nedsalk
as code owners
arboleya
previously approved these changes
Jan 26, 2024
arboleya
approved these changes
Jan 29, 2024
Dhaiwat10
approved these changes
Jan 29, 2024
|
Coverage Report:
Changed Files:Coverage values did not change👌. |
danielbate
changed the title
danielbate
changed the title
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.
We have been using a temporary coverage object on
rc/salamanderwhilst Vitest was not onmaster. Now #1495 has been merged, we can remove the temporary stage and generate a valid coverage object.