gh-action-pypi-publish
gh-action-pypi-publish copied to clipboard
The blessed :octocat: GitHub Action, for publishing your :package: distribution files to PyPI: https://github.com/marketplace/actions/pypi-publish
It seems like the action tries to upload all files and directories present in the `dist/` directory. This is fine as long as the build system did not add other...
Here is the [promised workflow](https://github.com/pypa/gh-action-pypi-publish/issues/22#issuecomment-720134921), for major and minor tag releases, which works with PEP440 versions. **Creates major+minor tags on** - 'normal' tags (e.g. `v2.0.0`) - post tags (e.g. `v2.0.0.post0`)...
It's got my attention that sometimes problems with transitive dependencies may reflect poorly on this action's ability to fulfil its purpose. Here's what's happened in the past: - https://github.com/pypa/gh-action-pypi-publish/issues/100 -...
Example image build+publish workflow: https://github.com/ansible/pylibssh/blob/devel/.github/workflows/build-manylinux-container-images.yml Example of an action pointer: https://github.com/fedora-python/tox-github-action/blob/9f7d1ff/action.yaml#L14
There's been some confusion with the tutorial so I'm documenting a few things that I'd like to improve (not sure if they belong to the tutorial or to separate guides):...
To make it easier for users to adapt to breaking changes in the action, having major version tags to rely on, instead of `master`, is a good thing for users...
I am not sure if this belongs here, but I am having an issue when using this Github Action. This is the link to the github run that failed: https://github.com/jampp/migratron/pull/25/checks?check_run_id=456554120...
The idea is to wrap `twine` invocation with the octomachinery framework which supports GitHub Actions out of the box. We need to specify an event handler for Actions and after...