Add publish job to the CI#55
Merged
Merged
Conversation
justvanrossum
force-pushed
the
add-publish-job
branch
from
7ecd7e5 to
c0189dd
Compare
9 tasks
justvanrossum
force-pushed
the
add-publish-job
branch
2 times, most recently
from
06986be to
781bda4
Compare
justvanrossum
force-pushed
the
add-publish-job
branch
from
781bda4 to
6f7378a
Compare
Member
|
Invite sent! |
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 still requires setting up Trusted Publishing on the PyPI side. If you add me as a maintainer I will do that.
The (GH) release notes will be set via the message of an annotated tag. I'll update the README with instructions if you agree with this approach. (This is an ongoing struggle for me, I don't really know what the "best practice" way of doing release notes is. I chose this way because the project doesn't have a CHANGELOG.md file.)