-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Seemingly wrong specification of GitHub Action for publishing to PyPI / TestPyPI #1108
Comments
It does work. If it doesn't do what you expect, maybe you've saved the token in the repo secret incorrectly (hint: check for trailing/leading spaces — it's the only problem I've seen people face; re-saving the token correctly is the solution).
It's unnecessary, it's already
I guess so. Although, it's just an example. I don't remember if I've come up with the release-tracking branch concept by the time I wrote the tutorial document. Feel free to send a PR updating this. Although, we'd have to remember to update the tutorial if I'll ever decide to make a v2 API for that action. I think I've left it pointing to the default branch just to avoid the burden of having to remember to update the tutorial document 🤷♂️ |
This patch reduces the emphasis on the `__token__` value of the `user` input since it's default anyway. It also adds a separate paragraph showing how to specify a custom username if the need be. Ref: pypa/packaging.python.org#1108
This will be fixed by #1113. |
The code at this link:
Does not match the usage from the README of the GitHub Action's website. Further it does not work.
In particular the above code has the following problems:
user: __token__
field is missing.@release/v1
.The text was updated successfully, but these errors were encountered: