Replace codecov with python-coverage-comment. #90
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
The codecov action has been failing for a few weeks. This replaces the use of codecov with python-coverage-comment, which is the tool used in other private repositories.
MichaelRoytman
force-pushed
the
michaelroytman/new-coverage-flow
branch
from
c28124b to
9894eb9
Compare
Coverage report
This PR does not seem to contain any modification to coverable code. |
zacharis278
approved these changes
Apr 26, 2024
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.
Description: The codecov action has been failing for a few weeks. This replaces the use of codecov with python-coverage-comment, which is the tool used in other private repositories.
JIRA: None.
Dependencies: None.
Merge deadline: None.
Installation instructions: None.
Testing instructions: None.
Reviewers:
Merge checklist:
Post merge:
finished.
Author concerns: List any concerns about this PR - inelegant
solutions, hacks, quick-and-dirty implementations, concerns about
migrations, etc.