History Graph in comparison view
### Describe the feature or problem you’d like to solve I need a Graph feature. I know this issue is duplicated with #1634 , but it is locked, and @outofambit allowed me to reopen this issue at #9444 . I implemented but I also think it needs more discussion. Sometimes I have to know where the branch comes from and when it was made. But I forget often where the branch comes from, and I have to look for history reading so many commit messages. I think this is not just for me. Human cannot remember what all branches come from. Merge direction is important too. Assume that I made a 'branch-a' from 'master', after some commits were pushed on 'master' and 'branch-a', made a 'branch-b' from 'branch-a'. I should merge 'branch-a' to 'branch-b' and 'master' to 'branch-a'. I should not merge 'master' to 'branch-b' directly and should not merge 'branch-b' to 'branch-a'. In order to know the merge direction, we have to make documents about all branches. But it's annoying, it will be better to see from History Graph. And we can see intuitively from History Graph whether juniors made mistakes in merging. As many people said, in order to aware that current branch is out of date, History Graph is also useful, too. ### Proposed solution The full graph is very complicated. Following the purpose of it, it will be better to show graph between only two branches. Many people want the classic thing. I mixed these needs with modern GitHub Desktop. So I propose below 
proposal: cmd/cgo: cgo without a C toolchain
Replace PowerToys Run with Command Palette
VPS with a vRack leg
Possibility of Portal 1 Code Inclusion
Introducing NewPlayer
Metrics for PRs are never expiring ("memory leak")
ship even more of the compiler in source form
Flatpak Application TRACKING ISSUE
History Graph in comparison view
### Describe the feature or problem you’d like to solve I need a Graph feature. I know this issue is duplicated with #1634 , but it is locked, and @outofambit allowed me to reopen this issue at #9444 . I implemented but I also think it needs more discussion. Sometimes I have to know where the branch comes from and when it was made. But I forget often where the branch comes from, and I have to look for history reading so many commit messages. I think this is not just for me. Human cannot remember what all branches come from. Merge direction is important too. Assume that I made a 'branch-a' from 'master', after some commits were pushed on 'master' and 'branch-a', made a 'branch-b' from 'branch-a'. I should merge 'branch-a' to 'branch-b' and 'master' to 'branch-a'. I should not merge 'master' to 'branch-b' directly and should not merge 'branch-b' to 'branch-a'. In order to know the merge direction, we have to make documents about all branches. But it's annoying, it will be better to see from History Graph. And we can see intuitively from History Graph whether juniors made mistakes in merging. As many people said, in order to aware that current branch is out of date, History Graph is also useful, too. ### Proposed solution The full graph is very complicated. Following the purpose of it, it will be better to show graph between only two branches. Many people want the classic thing. I mixed these needs with modern GitHub Desktop. So I propose below 
No comments yet. Start the discussion.