feat(data-index): generator + Cimas fixes for relaton-data-* Pages rollout - #55
Merged
Conversation
…llout Add a source-of-truth generator for the per-repo GitHub Pages index `_config.yml` of the remaining relaton-data-* repos (relaton/relaton#48), and fix the Cimas plumbing so the deploy workflow actually reaches them. - data-index/configs.yml + bin/gen-data-index-config: render each repo's repo-owned `_config.yml` (verified source / default-branch baseurl / pubid_class), matching how oasis/w3c/ids already own theirs. - lib + spec + Gemfile/Rakefile: rspec harness for the generator. - cimas.yml: correct stale branch: fields to real defaults (mostly v2), add adobe/easc/gost/jcgm/oiml, remove duplicate relaton-data-cie key, add iso to the data group, give jis its deploy.yml. - gh-actions/data/deploy.yml: trigger on [master, main, v2] + pull_request so v2-default repos publish (deploy still gated on the default branch). - data-index/README.adoc: rollout runbook + rendering-readiness tiers. Pubid flavors need a theme-side render fix before they render; tracked in the jekyll-theme-relaton-data-index hand-off.
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
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.
What
Adds a source-of-truth generator for the per-repo GitHub Pages index
_config.ymlof the remainingrelaton-data-*repos (relaton/relaton#48), and fixes the Cimas plumbing so the deploy workflow actually reaches them.Storage split (matches how oasis/w3c/ids already work): unique
_config.ymlis repo-owned, generated from a single table here; identical plumbing (deploy.yml,Gemfile.deploy) stays Cimas-managed.Changes
data-index/configs.yml+bin/gen-data-index-config— render each repo's_config.ymlwith verifiedsource(published INDEXFILE),baseurl(real default branch), andpubid_class.lib/+spec/+ Gemfile/Rakefile add an rspec harness (repo had none).cimas-config/cimas.yml— correct stalebranch:fields to real defaults (20 repos moved tov2); addadobe/easc/gost/jcgm/oiml; remove the duplicaterelaton-data-ciekey; addisoto thedatagroup; givejisitsdeploy.yml.cimas-config/gh-actions/data/deploy.yml— trigger on[master, main, v2]+pull_requestso v2-default repos publish (the reusabledata-deploy.ymlstill gates deploy on the default branch).data-index/README.adoc— rollout runbook + rendering-readiness tiers.Rendering readiness
Verified against the published indexes:
_typehashes): the 16pubid_classflavors — the theme plugin currently callsklass.new(**id), but those classes are modules (.createis the right call). Tracked separately forrelaton/jekyll-theme-relaton-data-index.Tests
bundle exec rake→ 11 examples, 0 failures. All changed YAML parses; cimas.yml structural checks pass; all 25 configs render valid.Notes
main(where the default-branch-gateddata-deploy.yml@mainthe master references lives).cimas.ymland left untouched:relaton-model-etsiremote points atrelaton-model-ccsds; allrelaton-model-*have emptyfiles:.