Closed
Conversation
Collaborator
|
Hi, @s3alfisc. We have the PyPi token now, but are a bit uncertain about where to place it. Does it belong into the |
Collaborator
|
Figured it out now, and the token is in place in Settings/Secrets/Actions as |
Member
Author
|
Closing as this has been covered with Tim's PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This CI workflow triggers a PyPi release whenever we release a new version via GitHub. It is taken from optimagic.
What we'd still have to do - create the API token and copy it to PyPi.