oci-release action: Option to drop branch name on tag push.#14
Open
Gerrit91 wants to merge 2 commits into
Open
oci-release action: Option to drop branch name on tag push.#14Gerrit91 wants to merge 2 commits into
Gerrit91 wants to merge 2 commits into
Conversation
|
I think every tag should always result in an artifact tag without a branch name. So essentially I'd mirror the behavior of releases. Alternatively we could also create a pre-release. What do you think? |
Contributor
Author
|
Very good point. Please check again, I now apply the tag of a tag push everywhere as an artifact tag. |
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.
Description
We need this in the releases repository where a tag push like
v0.1.0-rc.0should result into an artifact<name>:v0.1.0-rc.0and not<name>:develop-v0.1.0-rc.0.Used AI-Tools ✨