Add automated pypi release support
This PR will partially solve (the pypi part) issue #46. After this the selector package will be accessible via pypi pip.
- The project owners will need to 'Add a new pending publisher' in pypi https://pypi.org/manage/account/publishing/ with the name
selectororqc-selector(pyproject.tomlline 26 needs to be changed toqc-selectorif we wantpip install qc-selectorto work). - Create a new API token under https://pypi.org/manage/account/
- In the GitHub settings create a new environment secret with the variable name
PYPI_API_TOKENand paste the API token. - Create a new release to trigger the package build and publish to pypi.
@FanwangM can you take a look? Sorry for force pushing couple of times, had some pre-commit ci failures
Thanks for pushing this forward. I will look at it later. @kunikachandra
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 96.21%. Comparing base (
dbc2202) to head (6cf18ff). Report is 1 commits behind head on main.
@FanwangM should I create a new PR for setup.py or commit in this PR only?
Also, should I change the name to qc-selector instead of selector for the pypi package because selector is already taken by a previous project?
@FanwangM should I create a new PR for
setup.pyor commit in this PR only?Also, should I change the name to
qc-selectorinstead ofselectorfor the pypi package becauseselectoris already taken by a previous project?
You can keep adding new things into this PR. And we would prefer using the qc-selector. @kunikachandra
Thanks for helping with this.