Add branch:tag override syntax in branches.yaml#381
Merged
Conversation
Lets a build pull from one branch but publish under a different docker tag, e.g. `prototype/focil:focil` builds the prototype/focil branch and tags it `focil`. Replaces the previously unused `@` separator with `:`, which reads more naturally and frees `@` for future commit-pinning use. Applied to teku focil so it tracks consensys/teku@prototype/focil instead of the nonexistent `focil` branch (which is why scheduled builds for focil were failing).
🤖 qu0b-reviewerThe diff is clean and well-executed. Swapping No blockers. Looks good. 🦋Reviewed @ |
pk910
approved these changes
May 18, 2026
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.
Summary
branches.yamlnow accepts<branch>:<tag>entries — build from<branch>but publish under<tag>. Replaces the previously unused@separator (which read as a git commit specifier and was a footgun), freeing@for future commit-pinning.prototype/focil:focilso it tracks the actual upstream branch instead of the nonexistentfocil(which is why scheduled focil builds were failing).Test plan
python3 generate_config.pyruns cleanly — generatestarget.tag: focilwithsource.ref: prototype/focilfor teku focil.prototype/fociland publishesethpandaops/teku:focil.