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
Hello there! I'd like a similar idea, but more expanded:
Allow a vararg listing of refspecs, and visualize all n-1 refspecs with regards to the merge-base of the 1st refspec. Or, in lay-mans terms: I have a main and two branches that were incrementally merged to main. I'd like the subgraph that tracs merge-base of all of the aforementioned refspecs on the bottomo, the origin/main on top, and in-between the paths that those branches create with regards to main.
Would this be tracked here, or should I create a separate issue for it?
@stdedos You could well make a separate issue for it, to avoid that it gets lost. Also, I think some graphical/ascii art illustration would help to understand your proposal.
Problem: when walking the respository from
HEAD
, back-tracing of branches does notwork properly.Solution: back-trace the entire graph, but display only what is reachable from
HEAD
The text was updated successfully, but these errors were encountered: