chore(data): sync the vendored contract and catalogue - #19
Merged
Conversation
Copied from the engine, with the previews redrawn. The site remains the public URL of the contract, and builds a page per port out of the catalogue; this keeps both from falling behind.
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.
The vendored copy in
src/data/no longer matchedsp-night/sp-nightat
5a6183f4b5b424e8f878b78c6e565a902fc3a795.If this adds an entry to
ports.yml, merging it publishes thatport's page at
/ports/<slug>.npm run check && npm testpassed against the new values before thiswas opened, so the contrast policy and the no-raw-hex rule still hold.
An empty diff means the copy was already in sync.