Gitup: Optionally show all commit messages in map view

Created on 10 Aug 2016  路  7Comments  路  Source: git-up/GitUp

(for the current branch, of course.)

In this screenshot, I'm squashing commits on a feature branch. I've got tons of whitespace available, yet I need to constantly hit the up/down arrow keys to see which commit I'm going to squash with, etc.

It would be very nice if there were a way to show each commit's bubble, and not just the currently-selected one.

enhancement

Most helpful comment

I came here for the same reason. Already proposed! This application looks awesome, but this one feature is keeping me from using it: No visibility of commit and graph at the same time. (Command D) is OK, but disconnected from the graph. I think an in-line table style view like SourceTree is more effective, compact and effectively uses all the whitespace.

All 7 comments

Came here for a feature request. Turns out, it has already been proposed. I strongly second this feature! Would be a great addition to already an awesome application, awesome concept! Thanks! 馃憦

If you go to Repository -> Browser HEAD Ancestors (Command D) you can see the list of commits to HEAD within the map view

Great, thanks! Any chance of making the list more compact? Maybe, display only the commit message, but make the date and author fields optional?

And while we are discussing this, making the sidebar resizable would be really nice. :)

Thanks, @yonaskolb. It's helpful to know a similar feature exists, even if it does make the UI quite bizarre ;)

I came here for the same reason. Already proposed! This application looks awesome, but this one feature is keeping me from using it: No visibility of commit and graph at the same time. (Command D) is OK, but disconnected from the graph. I think an in-line table style view like SourceTree is more effective, compact and effectively uses all the whitespace.

Nicely said,

I think an in-line table style view like SourceTree is more effective, compact and effectively uses all the whitespace.

Additionally, navigating between the current Browse HEAD Ancestors and the graph is not very efficient, see also #196 .

Was this page helpful?
0 / 5 - 0 ratings

Related issues

richardtop picture richardtop  路  4Comments

adius picture adius  路  5Comments

jwiegley picture jwiegley  路  6Comments

swisspol picture swisspol  路  3Comments

lyqeyes picture lyqeyes  路  6Comments