Skip to content

Enable Codecov status API #6050

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

Closed
wants to merge 1 commit into from
Closed

Enable Codecov status API #6050

wants to merge 1 commit into from

Conversation

blueyed
Copy link
Contributor

@blueyed blueyed commented Jun 21, 2018

It was disabled in 68d2020, but likely accidentally - although there
was an issue for it already:
#4594, but

I think it is really nice to have feedback on how much of a diff is
covered etc - you can still merge PRs, especially when it is not
configured to be a required check.

I've intentionally left "comment: off", since that triggers
notifications (although I like it personally since it means that CI is
finished and there is a coverage report).

It was disabled in 68d2020, but likely accidentally - although there
was an issue for it already:
encode#4594, but

I think it is really nice to have feedback on how much of a diff is
covered etc - you can still merge PRs, especially when it is not
configured to be a required check.

I've intentionally left "comment: off", since that triggers
notifications (although I like it personally since it means that CI is
finished and there is a coverage report).
@blueyed
Copy link
Contributor Author

blueyed commented Jun 21, 2018

In general I would be in favor of removing the config file, but configuring with Codecov's UI - this way this unnecessary info (and history) is kept out of the repo.

@carltongibson
Copy link
Collaborator

@tomchristie turned this off. Lets ask him.

@rpkilby
Copy link
Member

rpkilby commented Jun 29, 2018

I'm in favor of re-adding the status check. Note that this would not reenable the codecov comment, which might have been the original intent in disabling codecov.

That said, I'd also be in favor of adding back the codecov comment. It's layout is configurable, and can be made more terse/less annoying.

@carltongibson
Copy link
Collaborator

Right, I think the general view here is against the status check, but maybe on the comment.

...layout is configurable, and can be made more terse/less annoying...

@rpkilby what's feasible in the range of tasteful here? (Could you add a screenshot?)

Also: Is codecov now correct?

@blueyed
Copy link
Contributor Author

blueyed commented Jul 2, 2018

@carltongibson

I think the general view here is against the status check,

s/is against/is not against/ ?

Here is an example comment: neomake/neomake#1989 (comment)

@carltongibson
Copy link
Collaborator

@blueyed. No. "against" was intended. Coverage is great and all but we don't want to make it a failure condition.

The comment you linked is pretty big. Is there a more minimal option. (I ask because, whilst I don't mind it personally, there is some scepticism.)

Also: Is codecov now correct?

@rpkilby
Copy link
Member

rpkilby commented Jul 6, 2018

The comment you linked is pretty big. Is there a more minimal option. (I ask because, whilst I don't mind it personally, there is some scepticism.)

Docs for the comment are here. There are four sections, but I think reducing this to either just the coverage graph or just the coverage diff is enough to convey the PR's impact, without being too verbose.

Also: Is codecov now correct?

You mean whether all files are covered now? It looks to be.

@rpkilby
Copy link
Member

rpkilby commented Jul 10, 2018

Closing in favor of #6077.

@rpkilby rpkilby closed this Jul 10, 2018
blueyed added a commit to blueyed/django-rest-framework that referenced this pull request Jul 10, 2018
Ref: encode#6077 (comment)

This is encode#6050
without the project status, and fixes/improves the comment added in
encode#6077.
carltongibson pushed a commit that referenced this pull request Jul 10, 2018
Ref: #6077 (comment)

This is #6050
without the project status, and fixes/improves the comment added in
#6077.
pchiquet pushed a commit to pchiquet/django-rest-framework that referenced this pull request Nov 17, 2020
Ref: encode#6077 (comment)

This is encode#6050
without the project status, and fixes/improves the comment added in
encode#6077.
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.

4 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy