Setup Codecov uploading and reporting #124
Merged
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.
When studying failed CI builds, I often find having to scroll past the codecov report tedious. In the rest of the MESSAGE stack, codecov is configured differently: a bot is picking up changes in coverage and reporting them as comments on the PR. For the rest of the stack, these are not just comments, but hard checks: should the PR reduce the test coverage (by too much), it will be rejected.
We don't have a policy like this with ixmp4 at the moment, so I'm not going to change that immediately. However, this PR tries to converge the different reporting styles: I have enabled the codecov bot for this repo, added a
CODECOV_TOKEN
secret, and configured codecov so that it should leave comments on PRs about coverage both within the changes proposed as well as the whole project in an informational way, i.e. not rejecting the PR because of lowered coverage.Please let me know what you think :)