It would be nice if adding files that are large would automatically track them with Git LFS. 

A filesize value as threshold would help (i.e. on add if file larger than 1MB -> git lfs track file)

If my repo is marked as favorite, I want to know if there are changes to the main/master branch while I currently have a feature branch checked out. It currently only seems to notify me if the main/master branch is checked out.

If the Branches pane is used to show/hide branches, then this may change the height of the displayed log tree. This has the effect of shifting the Graph window contents up or down.

If there is a commit selected and visible in the Graph window, then as possible the selected commit should be kept in-place as other branches are shown/hidden. Otherwise, the commit may move or even jump off the screen, which is confusing.

This won't always be possible (e.g. hiding a branch which is the only branch at the top or bottom of the visible area), but when it is it would be nice.

SmartGit shows an "Abort" button in a "The working tree is in merging-state" bar when you're in the middle of a merge. But, you have to know that to "merge" you click on the standard "Commit" button.

Proposal: add a "Merge" button to the left of the "Abort" button.

After running some git operations, I can see the git output by clicking on the green bottom status bar:

But showing only the last output is not enough to remember complex operations done successively. Access to its history other than just the last command is similar to running all git commands in a terminal, and it is pretty helpful to audit which git operation I had done and how they went. Just showing the last command is not enough to understand complex changes in the process.

I am not asking to remember the output after I close the Smartgint Standard Window, but to keep them while the window is open (as you already do with the Working tree and Log window). There is no see to use fancy formatting as done with the Working tree or Log Window. Just plain the text output of the command output is needed, and more than enough (and, of course, knowing the exit status of the git command is also essential; it just does not need to be fancy).

You could limit the maximum number of lines with a low-level property if you did not do this already. Because you are now saving only one command, it does not mean its output will be small.

On the log or working tree windows, I can have the git console output to see past git operations history.

This is useful for remembering hashes and whatever I had done with the project. Its history is similar to running all git commands in a terminal, and it is pretty helpful to know what Smartgit is doing behind the scenes and audit its git commands.

Emoji support was added in 20.2, see https://smartgit.userecho.com/communities/1/topics/720-emoji-support

But because of the very poor support of emoji in current git clients, when working on a repo using gitmoji it is necessary to write emoji codes instead of emoji characters : :bug: instead of 🐛for example.

Can a support to emoji codes be added ?

Sometimes I just begin to code a simple modification on the main branch.

Then I get back to Smartgit, and then I need to :

1. create a branch,
   
2. commit,
   
3. create a new pull request

With the new standard window, after switching to Smartgit I get redirected automatically in the "Local files" perspective.

The current branch is displayed just above the commit window... but it's easy to miss...

If I want to create a new branch I need to the History perspective, create a new branch, switch back to the Local files perspective... Not very convenient !

Ideally, I would love to be able to specify a new branch name and commit all at once.

Maybe simply add a new option in the commit window, just aside the "commit to: <branch>" label, a "new branch" button that would open a textfield where you would wrote the branch name ? Then fill the commit message and click on the commit button and boom, Smartgit automatically creates and checkout the branch, and then commit ?

Or more simply get a new branch button in the Local files perspective ?

I want modified files on top
in the Older UI's this is possible, in the standard window it is not.

In the log window, I use really often the "checkout" contextual option :

This is a good way to revert work without loosing it, and check for a previous behavior for example.

Unfortunately this option is not yet present in the standard window when right clicking on a current branch commit. Can it be added here also ?