Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typo in README #5

Merged
merged 1 commit into from
Oct 5, 2015
Merged

Fix typo in README #5

merged 1 commit into from
Oct 5, 2015

Conversation

blueyed
Copy link
Contributor

@blueyed blueyed commented Oct 5, 2015

No description provided.

@stevepeak
Copy link
Contributor

Thanks!

stevepeak pushed a commit that referenced this pull request Oct 5, 2015
@stevepeak stevepeak merged commit b1598e3 into codecov:master Oct 5, 2015
@blueyed
Copy link
Contributor Author

blueyed commented Oct 5, 2015

@stevepeak
Thanks for merging.

I've wondered about the Github integration of codecov.
Is it possible to have a check failure if changes from a PR are not covered by X %?
Or are the codecov checks limited to failures, in case the build failed altogether (encode/django-rest-framework#3394)?

What is the best-practice of handling builds from Travis matrix? Should it be uploaded only once, or for each combination of Python/Django/...?

@stevepeak
Copy link
Contributor

Check failure if changes from a PR are not covered by X %?

We do have a Github Status that does this check. A project (the entire project coverage) and a patch (the lines adjusted) coverage statuses. We have a ticket to add thresholds to them here: https://github.com/codecov/support/issues/88

codecov checks limited to failures

To insure accuracy of reporting Codecov, as of now, requires the CI state to be successful to compare coverage. If tests fail then some lines may not be hit and therefore cause coverage to decrease (very common). I you have suggestions on changing this feature please let me know how :)

best-practice of handling builds from Travis matrix

Codecov merges reports automatically, no setup required. The only specification you can optionally add is -e ENV_NAME to distinguish builds for example

@blueyed blueyed deleted the fix-readme branch October 5, 2015 10:28
@blueyed
Copy link
Contributor Author

blueyed commented Oct 5, 2015

@stevepeak
Thanks for your answers!

We do have a Github Status that does this check. A project (the entire project coverage) and a patch (the lines adjusted) coverage statuses.

They are not enabled for this repo though, are they? (#7)

@stevepeak
Copy link
Contributor

Your very welcome 👍

You can see the two statuses in the commits above. Codecov has not got an upload from the pending build yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants