Long branch names push the commit message out of the view. Shorten long branch names so at least a part of the commit message is visible.

A example for a long branch name:

custom/JDK8/dr-21654-some-jira-issue-title

Depending on the available space, shortening could be more aggressive. Everything from
custom/JDK8/dr-...jira-issue-title
to
cust...itle

could be possible.

The main aim should be to leave some space for the commit message.

Creating a new group is buried under the 'Move to...' context menu. Drag & Drop users have trouble discovering how to create a group.

Allow to select multiple repositories and Push, same as you can do with Pull. Handy when you've got a lot of changes in multiple repositories to synchronize.

I don't care how it's done: hovering over the commit row to see a multi-line tooltip, or selecting the row to vertically expand the row, or whatever... but it's important to be able to read a full commit message in the journal window. I hate having to bring up the log, then locate the same commit row and select it just to read whatever caught my interest in the journal window. I almost cringe at reading the journal window now, as a result. I might as well just turn it off.

Suggestion:

Currently, there are two separate 'Output' windows: in main window and 'Log'. I suggest to synchronize them, that is, make sure they have identical content at all times.

Rationale:

Depending on where you run a command from, its output ends up in one of those. I routinely run 'Rebase HEAD to...' from Log, then 'Continue rebase' from main window. Parts of the output ends up in 'Log', and another part in main window. To make matters worse, closing and reopening Log window during rebase will wipe its portion of 'Output'.

The same column recently added to the Files window in the main view.

Please, add https support to the lic-update page.

I find that sometimes if I close a view in the SmartGit workspace I forget how to get it back. Also, I imagine that different users have different tastes in what consitutes and efficient SmartGit workspace. It would be nice if the current layouts and dimensions of views could be saved as a named workspace that could be called up later.

Essentially, the Main and Review "Perspectives" are pre-defined workspaces. All I am suggesting is to allow users to name and use other arrangements of workspace views.