have adjusted base comparison use threshold #1056
Open
+57
−2
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.
I noticed that the coverage comparison we do when we apply adjusted_base behavior does not take
threshold
into account. Talked with @aj-codecov, we think that if a user definesthreshold
, they would expect it to be applied to all coverage comparisons, not just some.Therefore, I updated the comparison to include
threshold
if the user has set it.Right now threshold doesn't change the
message
- this follows the pattern with the otherproject
checks/status messages, wherethreshold
is used in the comparison but not explicitly stated in themessage
.