Add workflow: Release #14
Merged
Conversation
This file contains 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
|
Please update your repo. There were some important bug fixes. |
majabojarska
force-pushed
the
gh_workflow_deploy
branch
from
84996e8
to
9cb80e6
Compare
|
Rebased the changes onto latest changes upstream master branch. |
|
Thanks! |
|
I've added the PYPI_API_TOKEN as a "secret" in the repository. |
|
I don't know why but it's not working: |
|
Anyways, I fixed it by removing the "release" workflow and keeping only the "deploy" workflow. I always use the "draft a new release" button in GitHub to create new releases so there was no need for the "release" workflow. |
|
Yes, the "Release" step will fail if a release already exists. If you prefer to use draft releases manually that's also fine 👍. |
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.
Closes #5.
Changes:
v*(e.g.v1.0.5). This workflow creates a GitHub release and publishes the package to PyPI repository.v1.0.5results in package version1.0.5on PyPI. This also means that the package version won't be maintained via source code, but via Git tags.PYPI_API_TOKEN. See encrypted secrets page for details on how to do it.