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

add coverage workflow #261

Closed
wants to merge 1 commit into from
Closed

Conversation

danieleades
Copy link
Contributor

adds a coverage workflow using tarpauling and codecov.io

this will require setting up a codecov account to work (using github 0auth2)

@codecov-commenter
Copy link

codecov-commenter commented Dec 26, 2021

Codecov Report

❗ No coverage uploaded for pull request base (master@8092fc0). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##             master     #261   +/-   ##
=========================================
  Coverage          ?   74.80%           
=========================================
  Files             ?       49           
  Lines             ?     2624           
  Branches          ?        0           
=========================================
  Hits              ?     1963           
  Misses            ?      661           
  Partials          ?        0           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8092fc0...4435b40. Read the comment docs.

@matthiasbeyer
Copy link
Member

I am not sure whether we want this (a codecov account). At least I do not, at this time.

@danieleades
Copy link
Contributor Author

I am not sure whether we want this (a codecov account). At least I do not, at this time.

i understand the sentiment. It's not a painful process- it's a one-time login using github 0Auth and then it can access and comment on public repos without further setup or authentication. And the reports are quite nice...

shall i close this?

@matthiasbeyer
Copy link
Member

Leave it open, my opinion might change in the near future 😆

@danieleades danieleades force-pushed the chore/coverage branch 2 times, most recently from 55e7412 to 5add5ff Compare December 29, 2021 10:50
@epage
Copy link
Contributor

epage commented Oct 23, 2024

Superseded by #585

@epage epage closed this Oct 23, 2024
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