Repository navigation
fix(graph): join merge edges to existing branch routes - #2
Merged
Merged
Conversation
Member
|
Thanks. I have validated your pr, and it looks fine to me. |
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.
Merge edges could turn into the parent lane too early and pass through unrelated commit nodes when an existing first-parent route converges into that lane later. Route the merge through the existing branch span and reuse its color, keeping the junction aligned with that span.
Adds a regression test covering an unrelated node between the merge and its parent.
Validation: all 202 graph tests pass; TypeScript typecheck and git diff --check pass. Desktop visual validation has not been performed.