Skip to content

feat(data-index): wire machine-index flags; fold ietf into configs.yml - #72

Open
ronaldtse wants to merge 1 commit into
mainfrom
feat/pages-machine-index-wiring
Open

feat(data-index): wire machine-index flags; fold ietf into configs.yml#72
ronaldtse wants to merge 1 commit into
mainfrom
feat/pages-machine-index-wiring

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

What

Wires the machine-index flags from relaton/relaton#114 (contract v2) into the shared Pages deploy:

  • configs.yml: folds ietf in as a real Pages index (publish_data: true, pubid_class: Pubid::Ietf::Identifier). The previous deliberate exclusion is obsolete now that the combined v3 corpus ships.
  • DataIndexConfig#branding: emits pubid_flavor (derived from pubid_class"iso"/"ietf"/…) and publish_data into $GITHUB_OUTPUT.
  • data-deploy.yml: gem and git build steps forward both flags to relaton index --pubid-flavor / --publish-data. Callers stay byte-identical (no with: block).

Depends on relaton/relaton#114 merging first (deploy builds relaton-cli from relaton@main).

Tests

332 examples, 0 failures.

* configs.yml gains an ietf row (publish_data: true, pubid_class:
Pubid::Ietf::Identifier) — the combined v3 corpus is now a real
Pages index, so the previous deliberate exclusion is lifted.
* DataIndexConfig#branding emits pubid_flavor (derived from
pubid_class → "iso"/"ietf"/…) and publish_data for the shared
data-deploy.yml to pass to `relaton index --pubid-flavor` /
`--publish-data` (relaton/relaton#113 contract v2).
* data-deploy.yml's gem and git build steps forward both flags;
callers stay byte-identical (no with: block).
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@ronaldtse