Auto pypi package push

[danielbeach]

@jcorrado76 Right now to push a new version out to PYPI, I'm doing that locally with poetry , with poetry build and poetry publish, to get a new package out on PYPI. Can we automate this somehow with GitHub actions?

Not sure we want a new PYPI package published every time we push to main? I'm assuming I can load some ENV Vars for GitHub actions so it has permissions to do the push, just curious on thoughts on if it should be every time we merge to main or something else?

[jcorrado76]

@danielbeach - Certainly! In #23, I separated the triggers for running CI (GitHub actions workflow triggered by a push to main, or a push to feature/), and running CD (the publish to PyPI happens upon a release event).

So to run all the tests and linting, you need to push to a branch named "feature/[something]". And it's also triggered upon pushes to "main". But we shouldn't allow people to push to main. People should only be able to merge upon approval of a PR (and merges count as pushes and will trigger the CI on main).

To run the workflow that publishes to PyPI, you need to create a new release in GitHub.

To close this issue, maybe one of us can try bumping the SemVer version number (to like 0.1.0-test or something), and test the publishing to the Test PyPI endpoint.