MAINT: Add codecov.yml config file to reduce noise in PRs
#509
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
|
Best reviewed: commit by commit
Optimal code review plan
|
|
Could you show an example of what you're trying to avoid? |
|
Example #506 - this will hide the codecov/project check from the list and show up as building okay in github. |
|
Oh, got it. Right, I forgot that we don't run all the tests on PRs. |
effigies
reviewed
Apr 29, 2020
|
This is fine by me. |
mgxd
approved these changes
Apr 29, 2020
Removes the "project" target from comments in PRs because the segregated testing of niworkflows (masks, pytests, reportlets, ...) makes almost all PRs to be under a decent project threshold (and hence show up as failed).
oesteban
force-pushed
the
maint/codecov-config
branch
from
0de02a4 to
bfc407e
Compare
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.
Removes the "project" target from comments in PRs because the segregated
testing of niworkflows (masks, pytests, reportlets, ...) makes almost
all PRs to be under a decent project threshold (and hence show up as
failed).