feat(visualize): render the cross-repo flow as per-repo lanes - #362
Merged
Merged
Conversation
Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
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 a cross-repo graph granularity that renders the multi-repo flow: the primary repo's pipeline as the root lane, a lane per dependent satellite it coordinates, and the satellite-to-primary notify edge, so a reader sees the cross-repo artifact flow in both directions.
The view model gains a render-agnostic lane primitive and cross-repo edge kinds; the Mermaid subgraphs and edge styling stay in the emitter. A manifest with no externals renders just the primary pipeline. The existing jobs, env, and stages projections are untouched (their goldens are unchanged), and the stages refactor that extracts a shared stage helper is behavior-preserving.
Verification: golden, determinism, no-externals, and satellite-only unit tests, plus a hermetic file-based integration test through the cascade graph command. Additive only: no schema or generator-output change.
Closes #305.