Collect base coverage when switching is skipped #239
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
Keep collection base coverage data even if switching is skipped due to an existing base coverage file.
|
That makes total sense, sorry about that! |
ArtiomTr
approved these changes
Mar 3, 2022
|
@all-contributors please add @Raigen for code |
|
I've put up a pull request to add @Raigen! 🎉 |
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.
Keep collection base coverage data even if switching is skipped due to an existing base coverage file.
With #237 switching branches is skipped when a file for the base coverage is provided. But the coverage data of the base report is not collected when the branches are not switched.