You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating a GitHub release, we should support specifying that the release is a draft.
Draft releases are regular releases, but they are not visible to people who browse the releases tab in the repository. It is useful as a validation step before actually publishing the release to the wild.
For PyCI, draft releases take on another meaning by not publishing wheel packages to PyPI.
Essentially, this option should do everything a normal release does, except for any operations that expose the release to the public internet.
The text was updated successfully, but these errors were encountered:
iliapolo
added
feature
This issue introduces a new feature
minor
Implies this code change should bump the minor version of the project
labels
Jul 27, 2019
When creating a GitHub release, we should support specifying that the release is a
draft
.Draft releases are regular releases, but they are not visible to people who browse the
releases
tab in the repository. It is useful as a validation step before actually publishing the release to the wild.For PyCI, draft releases take on another meaning by not publishing wheel packages to PyPI.
Essentially, this option should do everything a normal release does, except for any operations that expose the release to the public internet.
The text was updated successfully, but these errors were encountered: