Manual trigger mechanism for the release process#222
Draft
ubitux wants to merge 4 commits intoNopeForge:mainfrom
Draft
Manual trigger mechanism for the release process#222ubitux wants to merge 4 commits intoNopeForge:mainfrom
ubitux wants to merge 4 commits intoNopeForge:mainfrom
Conversation
This will allow building releases from any branches without conflicts with existing tags.
This allows triggering the release workflow from a random branch for testing purpose.
ubitux
force-pushed
the
release-dev-test
branch
from
469114b to
7b3148c
Compare
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
1 participant
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.
Draft for now because because of the
ref_namenot working for the "child" release workflows, only valid in therelease.ymlworkflow