Strip language surfaces from hyperpush root#10
Merged
Conversation
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.
Summary
Strip the copied language/toolchain tree out of the product repo so the root is genuinely product-only again.
This keeps:
mesher/mesher/landing/mesher/frontend-exp/and removes the copied Mesh language/compiler/docs/registry/packages-site tree that does not belong in the product repo.
What changed
compiler/website/packages-website/registry/examples/tests/tools/benchmarks/articles/mesh-slug/.gsd/,.cargo/,.githooks/, and the language release/workflow/verifier stackREADME.mdCONTRIBUTING.mdSUPPORT.md.github/CODEOWNERS.github/ISSUE_TEMPLATE/*.github/dependabot.yml.gitignore.github/workflows/ci.ymlmesh-lang, buildsmeshc, runs the Mesher maintainer verifier, and builds bothmesher/landingandmesher/frontend-exp.github/workflows/deploy-landing.ymlmesher/scripts/verify-maintainer-surface.shscripts/verify-m051-s01.shmesher/README.mdmesher/.env.examplefrontend-expproduct-owned under:mesher/frontend-exp/mesher/meshermesher/mesher.llmesher/outputExplicit ownership note
frontend-expstays with the product repo.This branch keeps it at:
mesher/frontend-exp/It does not move back into
mesh-lang.Verification
bash scripts/verify-landing-surface.shbash scripts/verify-m051-s01.shnpm --prefix mesher/landing ci && npm --prefix mesher/landing run buildnpm --prefix mesher/frontend-exp ci && npm --prefix mesher/frontend-exp run buildNotes
hyperpush-org/hyperpush-monotohyperpush-org/hyperpush. This PR is opened against the redirected repo.mesh-langsplit-boundary wrappers may need a follow-up to match the slimmer product-root bundle/CI contract exactly.