Fix scoverage #297
Merged
Fix scoverage #297
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
Pull Request Test Coverage Report for Build 3073099105
💛 - Coveralls |
mdedetrich
force-pushed
the
fix-scoverage
branch
from
5186c43 to
d1dd63b
Compare
mdedetrich
force-pushed
the
fix-scoverage
branch
from
d1dd63b to
eb4f0c4
Compare
mdedetrich
requested review from
reta,
RyanSkraba,
snuyanzin,
ahmedsobeh and
jlprat
snuyanzin
approved these changes
Sep 17, 2022
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.
About this change - What it does
This PR updates scoverage.
Why this way
Ever since #261 was merged scoverage wasn't working, this PR fixes that. See scoverage/sbt-coveralls#199 and scoverage/scalac-scoverage-plugin#497 for the reason why scoverage broke in the update