Enable automated release tagging when PR from branch's 'release-xxxx'#329
Merged
Conversation
davidcollom
requested review from
aidy,
hawksight,
jontutcher,
joshw123 and
maria-reynoso
hawksight
reviewed
Feb 14, 2025
davidcollom
commented
Feb 14, 2025
aidy
approved these changes
May 2, 2025
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
3 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 a quality of life for maintainers.
Once a PR from a branch
release-xxxxis merged, this workload will push a tag from thevx.x.x.This will then trigger the full release workflow publishing the chart and container images.
Edit: I've been using this on another internal project and its been working great! 👍