gh-action-pypi-publish
The blessed :octocat: GitHub Action, for publishing your :package: distribution files to PyPI, the tokenless way: https://github.com/marketplace/actions/pypi-publish
Not yet testedsource: GitHubhomepagePythonBSD-3-Clausecommit dc37677b2e1c
Python, BSD-3-Clause licensed. The project labels itself: actions, github action, github actions, github actions python, oidc, pypa guide, pypi and python.
gh-action-pypi-publish has not been verified yet.
Measured by Argusic on a fresh machine every time. Every number links to its evidence.
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
No recorded runs.
Topics (from GitHub)
actionsgithub-actiongithub-actionsgithub-actions-pythonoidcpypa-guidepypipythonpython-packagingreleaserelease-automationrelease-helpersecretstestpypitwineuploadworkflowworkflow-automationworkflows
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/gh-action-pypi-publish)Questions
- Does gh-action-pypi-publish run?
- gh-action-pypi-publish has not been fully verified yet. No recorded run has produced a verdict yet.
- How did Argusic test gh-action-pypi-publish?
- On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
- Where is the evidence for gh-action-pypi-publish?
- All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.