You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: History graph loses its lines below a second root commit #25360
In any repo, merge an unrelated history (git merge --allow-unrelated-histories other) or create an orphan branch and merge it back.
Open the history graph for a range that includes the second root commit.
Below the root commit of the merged-in history, the lane that still leads to the first parent's history disappears: the graph shows a broken line, and the rows below start with no incoming lane.
Minimal model repro: buildGitHistoryViewModels([M(parents A,V), V(root), A(parent B), B(root)]). The V row receives lanes [A, V] but emits [], so the A row receives no lanes at all.
Root cause
src/shared/git-history-graph.ts:114 wraps the lane carry-forward loop in if (historyItem.parentIds.length > 0). A root commit has no parents, so the loop is skipped and every other lane still in flight is dropped instead of only ending the root's own lane. It is invisible in single-root history and only shows once a second root exists.
Activity