IONOS(ci): forward the source ref name to the remote trigger (HDNEXT-1373) - #326
Merged
printminion-co merged 1 commit intoAug 25, 2026
Merged
Conversation
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.
Port of #325 to the
ionos-dev-v32lane — identical two-line change plus a comment.Adds
GITHUB_REF_NAMEandGITHUB_REPOSITORYto the remote trigger so the downstream release report can name the RC or branch a build came from. See #325 for the rationale and the review.Draft until the v32 lane is the one being triggered. Note that which lane actually fires is decided by the
REMOTE_TRIGGER_NC_VERSION/REMOTE_TRIGGER_RC_BRANCHrepo variables (currentlyv31/rc/web-v31-1), not by which branch carries this code — so merge order across the three lanes does not matter.HDNEXT-1373