renames the workflow from Python Package to CI Build,
Adds CI-build workflow status badge,
Adds Coveralls step in CI-build (the step is run only when python==3.8 to avoid duplicates),
Adds Coveralls coverage badge,
Updates setup.py to simplify code and add more specific supported python languages,
Adds Pypi's supported python version badge.
Build success:
A successful workflow run on my forked repo can be seen here.
A sample demo of the readme badge output can be seen here.
A sample demo of coveralls webpage can be seen here.
Issues:
coveralls requires secrets.COVERALLS_REPO_TOKEN (as seen in ci-build.yml). @johnklee needs to set this secret up following Coveralls Official Tutorial.
the README's current coveralls badge link connects to wkCircle/fpu/badge.svg?branch=19-badges, @johnklee needs to change it to johnklee/fpu/badge.svg?branch=master.
I didn't do this because I wanna show the demo and at the same time I don't have the permission of the original repo.
Question:
Is there a way that you can download the branch 19-badges and continue to work on it, so you can test everything on your side with your permission?
This PR is related to #19
The PR
Python Package
toCI Build
,setup.py
to simplify code and add more specific supported python languages,Build success: A successful workflow run on my forked repo can be seen here. A sample demo of the readme badge output can be seen here. A sample demo of coveralls webpage can be seen here.
Issues:
secrets.COVERALLS_REPO_TOKEN
(as seen in ci-build.yml). @johnklee needs to set this secret up following Coveralls Official Tutorial.wkCircle/fpu/badge.svg?branch=19-badges
, @johnklee needs to change it tojohnklee/fpu/badge.svg?branch=master
.I didn't do this because I wanna show the demo and at the same time I don't have the permission of the original repo.
Question: Is there a way that you can download the branch
19-badges
and continue to work on it, so you can test everything on your side with your permission?I will mention the status in the issue #19