Import dataset and implement build script and CI#1
Merged
Conversation
This imports the curated std-replacement data from crates.io (see rust-lang/crates.io#13855) into per-crate TOML files under `data/`, with the descriptions rewritten from HTML to Markdown.
This reads every `data/*.toml`, validates that each carries exactly the required fields (`description`, `url`), and writes a sorted `build/all.json`. It collects all TOML parse and field errors in one pass and exits non-zero on any.
The `build` job runs on pushes to `main` and on pull requests, validating the dataset via `build.py` and uploading `build/` as the Pages artifact. The `deploy` job publishes that artifact to GitHub Pages, gated to `main` pushes.
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.
This imports the curated std-replacement data from crates.io (see rust-lang/crates.io#13855) into per-crate TOML files under
data/, with the descriptions rewritten from HTML to Markdown. The starting set islazy_static,once_cell,matches, andnum_cpus.build.pyreads everydata/*.toml, validates that each carries exactly the required fields (description,url), and writes a sortedbuild/all.json. It collects all TOML parse and field errors in one pass and exits non-zero on any, so a bad PR surfaces every problem at once.The build runs on pull requests and pushes to
main, validating the dataset and uploadingbuild/as the Pages artifact. The deploy job takes that artifact to GitHub Pages and only runs onmain.