Using GitHub Actions to publish releases to pip/pypi (Developer demo)

This video demonstrates how easy it is to make new releases of a python package on GitHub, and publish it to pypi.org.
Learn more about cf-remote:
cfengine.com/company/blog-det...

[@oziousmegasus9201]

github now has build-in script for pypi and only requires minor changes. I am still grateful for your instructions.

[@mujykun]

thanks for the easy demonstration.

[@AidenEllis]

This really helped a lot

[@nielsuit]

Thanks for the video. Checked out your repo too. I'm curious how your `twine upload dist/*` gets its credentials? You add the secrets to the environmental variables but never call them?

[@cfengine]

You don't call environment variables, they are available to the programs you run. Any program can check for environment variables (for example using os.getenv() in python). Here are the environment variables twine looks for: twine.readthedocs.io/en/latest/#environment-variables As you can see, we are using TWINE_USERNAME and TWINE_PASSWORD in the GitHub Action: github.com/cfengine/cf-remote/blob/35c3ac889c7c8a7642a559b84d0ec16b9710adf5/.github/workflows/python-publish.yml#L27-L28

[@somethingfacty4204]

But how to setup pypi password and username for uploading like this😅 Because i don't this

[@cfengine]

Create an account on pypi.org/

[@yotamarker]

fake tutorial : `long_description` has syntax errors in markup and would not be rendered on PyPI.