docs(contributing): explain the polyrepo rationale - #44
Merged
Merged
Conversation
Both are imported by source (mermaid via dynamic import in the Mermaid MDX component, unleash-client in the flags client) and are already listed in knip's ignoreDependencies, but were missing from package.json, so `tsc --noEmit` failed to resolve them.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Task link: n/a
Documents why Omni uses a polyrepo/metarepo layout (the section previously described only the mechanics): license boundaries as repo boundaries, independent release cadence, clean per-service audit trails, tooling performance, and the coordination tradeoff. Also fixes an "Exmaples" typo and declares the
mermaid/unleash-clientdeps thattsc --noEmitneeds.Test Steps