chore(data): sync the vendored contract and catalogue - #16
Merged
Conversation
Copied from the engine, with the previews redrawn and the derived assets regenerated. Adds the Helix entry, and the `editor` group with it, which publishes /ports/helix. Done by hand because GitHub Actions is in a major outage and the fan-out that normally opens this pull request could not run. The steps are the ones sync-ports.yml performs, in the same order.
The catalogue moved again while this branch was open: the Alacritty entry no longer describes `bright_foreground` as a key the theme leaves alone.
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.
Adds the Helix entry to the vendored catalogue, and the
editorgroup with it.Merging this publishes
/ports/helix.Why by hand
GitHub Actions is in a major outage, so
sync-ports.yml— which normally opensthis pull request when the catalogue changes on the engine's
main— has notrun. Nothing is misconfigured; there are simply no runners.
The steps here are the ones the
sitejob performs, in the same order:palette.json,roles.json,ports.yml,copy.ymlfrom the enginecontrast.jsonfromspn check --jsonpublic/previews/npm run assets— the README tables and the per-port OG cardsnpm run check && npm test && npm run buildStep 4 is the one added in sp-night/sp-night#11. Without it this would have
failed at step 5, which is exactly why a new port could not reach the site
before.
Checked
astro check0 errors, 56 tests, build complete — 11 pages, includingdist/ports/helix/index.html. The/portsindex shows the Helix card under anew Editors group, and the README ports table lists it.
Only the Helix previews are new; the other four already matched.
Note on deployment
Pages is in the same outage. Merging this will not deploy until it recovers —
deploy.ymlwaits rather than failing, so it should land on its own.