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
This is expected behaviour, as these branches are seen as a different category than main or master (e.g. feature branches). So display in a different column is intentional.
Thank you @mlange-42 for your answer. I understood it was a gitflow thing when I tried switching the mode to none.
Now, it might be the desired layout for gitflow users, but it seems wrong in other cases. For someone coming from "git log --graph" and not using gitflow, it looks like a bug. Maybe the solution would simply be to default the mode to none?
I can understand from a new user point of view that it is a surprise.
I'm changing this to a feature request.
A good implementation that also works for advanced users would allow a per-user setting of default model.
Activity
mlange-42 commentedon Apr 23, 2026
This is expected behaviour, as these branches are seen as a different category than
mainormaster(e.g. feature branches). So display in a different column is intentional.plafrance commentedon May 2, 2026
Thank you @mlange-42 for your answer. I understood it was a gitflow thing when I tried switching the mode to none.
Now, it might be the desired layout for gitflow users, but it seems wrong in other cases. For someone coming from "git log --graph" and not using gitflow, it looks like a bug. Maybe the solution would simply be to default the mode to none?
[-]Descendant branches of main incoherently rendered[/-][+]Change default model to none[/+]peso commentedon Oct 28, 2026
I can understand from a new user point of view that it is a surprise.
I'm changing this to a feature request.
A good implementation that also works for advanced users would allow a per-user setting of default model.