OpenAPITools / OpenAPITools/openapi-generator-pip
Authorize PyPI with OICD
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 31
- Forks
- 8
- Avg merge
- 5h 51m
- Merged PRs (30d)
- 3
Description
For GitHub Actions that publish packages, configure OAuth on the PyPI side to authorize each request individually. This allows to remove the API token from repo secrets.
Docs:
https://docs.pypi.org/trusted-publishers/
https://docs.pypi.org/trusted-publishers/adding-a-publisher/
My example:
https://github.com/eggplants/getjump/blob/master/.github/workflows/release.yml#L23-L36
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the repository's GitHub Actions release workflow and identify how the current PyPI API token is supplied. Read the linked PyPI Trusted Publishers documentation and compare the workflow with the linked example; done means packages publish successfully through per-request authorization without a repository API token.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100