When other branches get far ahead of your current one, your current branch is not displayed

[hirden]

When you are on a branch which then get passed in commits by another remote, your current "branch track" is not displayed.

[Ajedi32]

...scroll down? 😜

[hirden]

Well yes :P , it pops up when I scroll down, but the dotted line should, I assume, always be shown?

[hirden]

Also, should not your current branch be the focus of the view?

[Ajedi32]

I'd expect a view similar to what you get in the command line with git log --all --oneline --graph --decorate. Either way, the nonexistent "staging commit" should probably always be at the top of the screen.

[FredrikNoren]

Hm yeah that's a bit ugly, you're right it should always be shown.

[jamesjnadeau]

This happens to me a lot, I"m ok with scrolling, but I'm going to try and look into seeing if we can detect this case, then make the interface load up what it needs to display properly.

[FredrikNoren]

@jamesjnadeau I've been toying with an idea of "collapsing" the commits, so that it would just show one ball with a number on it instead of all of them

[jamesjnadeau]

I like that idea, but would require more work :)

[daedalus28]

I know this is an old ticket, but I wanted to bring this up as I have a use case where scrolling isn't really viable. In my project I have some branches that are very far behind and when switching to them (using the fancy new branch picker dropdown 😄), I can't see the current commit to merge in the latest version of the main branch. These branches are few months behind and there are so many commits to scroll though that I really can't find it and have to jump to the command line to make it work.

The commit collapsing idea is cool, but even a "jump to" or just "load n more months of history" command would do it.