-
-
Notifications
You must be signed in to change notification settings - Fork 409
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 docstr-coverage badge #1680
Conversation
Before a pull request is accepted, it must meet the following criteria:
|
Codecov Report
@@ Coverage Diff @@
## master #1680 +/- ##
=======================================
Coverage 61.26% 61.26%
=======================================
Files 63 63
Lines 5798 5798
=======================================
Hits 3552 3552
Misses 2246 2246 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is pretty smart - jsonbin.org seems like a useful tool 👍
@epassaro needs the conflict fixed then we can merge |
1f47d15
to
c16e15d
Compare
Done. |
c16e15d
to
df6eede
Compare
* auto-updatable docstr-coverage badge * add badge to README.rst * fix broken azure badge * change condition before merging
Description
Use jsonbin.org RESTFUL API and shields.io endpoint to create a badge for
docstr-coverage
workflow.master
branch.Motivation and context
Currently we don't have a way to see what's the result of
docstr-coverage
without running it.How has this been tested?
Tested on my fork. Results uploaded at: https://jsonbin.org/tardis-bot/badges/tardis/docstr-coverage
Examples
Type of change
Checklist