Let me compare two local branches by its commits and view diff between its files.

When viewing a log with multiple branches, SmartGit often shows the commits non-chronologically. SmartGit should always show commits in chronological order whenever possible. (Obviously in some cases, such as when history is modified, it may be impossible to show commits in chronological order while maintaining proper parent-child ordering, but SmartGit seems to show commits non-chronologically even when not necessary.)

Here's an example where SmartGit is showing commits non-chronologically:

... regardless of whether a toplevel module is updated/fetched.

Optimally on a per-submodule basis, but an all-or-nothing switch is better than no support.

(topic description on 2017-03-10)

It would be nice to have a button to pull all submodules on the currently selected branch.

In the Repository Settings in one of my projects I have configured to sign commits with my GPG key:



Now I don't want to use GPG anymore (that's why I deleted Gpg4win on my computer) but SmartGit always tries to sign my commits using "gpg2.exe".

I unchecked the "Sign all commits" option in my repository settings but if I add new repositories in SmartGit, then SmartGit still tries to sign them with GPG (even though the checkboxes are turned off).

What I am missing is a general setting within SmartGit, where I can configure GPG Signing on a global level.

As user I wish to be able to set an option during merge operations (including Git flow operations) to use the following "git merge" options:

-Xignore-space-change -Xignore-space-at-eol -Xignore-all-space

On GitHub (at least), a pull request has a separate title and description. An important difference between the two fields is that references to bugs or other PRs are detected only in the description.

SmartGit's "create pull request" dialog has a single large text field named "title and description". I think it might improve usability to either split this field in two, or to draw a line after the first paragraph (at the first newline) to indicate to the user where the title ends and the description begins. While a regular user of this feature will not make this mistake often, it is a bit annoying to both me and the repo owner I'm sending a pull request to if the whole description ends up in the title and no backlink appears in any bug I've referenced in the pull request text.

If there are hosting providers where this distinction does not exist, SmartGit can just merge the two fields' content again, if necessary (at the point the dialog appears, SmartGit should be aware where it will be sending the PR).

When the most of my work is on a single repository, I don't need the repositories bar on the left hand side. But if I lose that bar, I won't know which branch I'm working on.

So, it's much cleaner if we show at least the branch name on the very spacious bottom status bar.

Please review an option to set the default settings for a group. Often, we do have two groups: job/home. At home I would like to sign all commits with the same key. In the same time my private email is used. At work I would like to use different email and username. I could do it in a console for sure... Thank you.

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.