Skip to content

Use PYPI_API_TOKEN instead of pypi_password as secret name in examples #52

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 13, 2020
Merged

Use PYPI_API_TOKEN instead of pypi_password as secret name in examples #52

merged 1 commit into from
Dec 13, 2020

Conversation

scop
Copy link
Contributor

@scop scop commented Dec 12, 2020

GitHub secrets are customarily spelled in uppercase, and in PyPI terms we're dealing with API tokens here, not passwords.

I think these tweaks make things slightly easier to follow, and decrease likelihood of actual PyPI passwords ending up in secrets when careless.

GitHub secrets are customarily spelled in uppercase, and in PyPI terms
we're dealing with API tokens here, not passwords.
Copy link
Member

@webknjaz webknjaz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, @scop! It's a great idea!

The reason these were lowercase is that GitHub used to allow those and only in recent months they've started normalizing names to uppercase.

P.S. It'd also be useful to update https://github.com/pypa/packaging.python.org/blob/master/source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants