To create a release package file in draft - #6461
Merged
Merged
Conversation
This is to allow final confirmation of the created release file. Release files in draft form cannot be downloaded by the general public.
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 is to allow final confirmation of the created release file. Release files in draft form cannot be downloaded by the general public.
This is related to #6133.
While #6133 makes a release announcement as soon as the tag is pushed, this patch creates the release announcement in a stubbed state, giving the administrator room for final review.
Since it will be invisible to everyone except the project manager, the release status must be changed if the file is to be made available to the public.
The release message can also be changed at this time.