Configure codecov3 #323
Merged
Configure codecov3 #323
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
|
Have also updated documentation on the github actions in the dev repo: https://github.com/mixOmicsTeam/mixOmics-Dev/blob/main/Resources/Development%20Resources/4.%20Repositories/4.1%20GitHub%20Repo%20Management/4.1.4%20Github%20actions.md |
|
codecov reports now appear to be generated and pushed to app.codecov.io |
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.
used
usethis::use_github_action("test-coverage")to add yaml file for code coverage report generation and pushing to codecov. Also set up github repo secret CODECOV_TOKEN. Coverage report should be published here: https://app.codecov.io/github/mixOmicsTeam/mixOmicsRemaining issue: report is published on codecov but shows error 'Missing base commit: unable to compare commits because no base commit was found'. This may be because the action was run not on master branch as it had done previously, hopefully will be solved with this PR to master.