Uh oh!
There was an error while loading. Please reload this page.
fix(cimas): relaton-data-ietf lives on main, not master - #71
Merged
Conversation
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
relaton-data-ietf's real default branch is
main(renamed frommaster), but cimas.yml still targetsmaster. Because ietf has nodata-index/configs.ymlrow (deliberately — it publishes no per-flavor branding), the branch-consistency spec never checked it, and the 2026-08-17 wave synced its workflows onto a branch the Pages gate can never publish from.This surfaced live: the Gemfile-fix PR (#6) auto-based on
mainwhile the Cimas wave PR (#7) based onmaster, and the two branches diverged.