I spend a lot of time browsing through the commit graph, and doing things ike "reveal commit" on a branch, which often takes you far away from your previous focus: I often find myself instinctively clicking the back/forward buttons on my mouse, expecting to cycle through the commit selection history... would be nice.

Currently, files in the Local Files and History views are shown as list. The user only has the option whether to show it as name (path) or path/name. Depending on the directory structure the path part can get quite wide which might cause issues in the History view:

Alternatively, there could be an option to show the files as tree-like list adding directory entries for each parent directory (without a way to collapse directories):

This might require less horizontal space (but a lot more vertical space).

It is often useful to see just most recent branches and search among them, best would be having also the possibility to maintain the view by folders (each folder containing branches sorted by head date)

Integrations with tools like atlassian bitbucket/jira helps creating prefixes to group branches based on usual '/' depending on the task type (feature, bug, ...), the problem comes when multiple users need personal branches, in this case to avoid first level folders floading it is be helpful to nest these branches as "personal" but SmartGit doen't handle a second level of folders

It drives me bonkers when I branch then commit, only to find that I committed on the branch I was on before :)

This happens to me because "Add Branch" is the default button in the Add Branch dialog, and it leaves me on the old branch.

I often want to know what commit is the most recent shared ancestor for two commits.

Suggestion: when more than one commit selected in Log view, add "Select Mutual Ancestor" to popup menu. This would unselect the selected commits and then select (and show) the most recent commit that is an ancestor of all selected commits (as "git merge-base" would).

in File Compare after you're done with take left/take right, you have a Save button, would be nice if you also had a Stage button next to the Save button

SmartGit maintains a settings directory for each used major version. Hence, when upgrading SmartGit, settings directories of previously used SmartGit versions remain. When launching SmartGit in a non-preview mode with a registered, valid license, it could offer to delete settings directories from previous versions.