Update release instructions#83
Merged
Merged
Conversation
Member
Author
isidentical
reviewed
Nov 26, 2022
|
|
||
| Click on the action and scroll down to the bottom of the page titled "Artifacts". Download `dist.zip`. | ||
|
|
||
| Upload the wheels to testpypi. |
Contributor
There was a problem hiding this comment.
I think it might be helpful for people with less experience to also include the twine config here (with redacting the credentials) since --repository=testpypi is a config-specific thing.
isidentical
reviewed
Nov 26, 2022
Co-authored-by: Batuhan Taskaya <isidentical@gmail.com>
isidentical
approved these changes
Nov 28, 2022
Contributor
isidentical
left a comment
There was a problem hiding this comment.
Looks great, and the link to the official packaging tutorial is a nice addition 💯
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
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.
Which issue does this PR close?
Part of #7
Rationale for this change
Document how to do a release based on recent experience
What changes are included in this PR?
Docs
Are there any user-facing changes?