Add manual release process #866
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
|
coming back to this, to be clear this can be forced if needed but has to be triggered differently then normal way we do a release so we can attempt a release if it fails and we want to force it we can then use this? |
|
want to confirm before i merge @Tompage1994 |
Yes this is simply an additional workflow to run manually if needed when CI is broken |
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.
What does this PR do?
Adds a manual release process for when the CI is broken to enable admins to push through releases which are of sufficient quality/
How should this be tested?
It's the same pipeline, just with the CI removed and an input for the version to release.
Is there a relevant Issue open for this?
No
Other Relevant info, PRs, etc
#831 related