Occasionally, I need to review the code around a particular commit.
However, I can't seem to find a way to directly navigate to a particular commit without applying any filters.

I found it on gitkraken

but on smartgit

It would be nice if the branch structure in the Standard Windows view could be set like in the Log Windows view where SmartGit shows local branches and remote branches in a tree view. Also branches are grouped by paths:

I think the UI would be more consistent if the layout of "Local Files" and "History" tabs would be similar in the Standard Window:

History in the center of the window and commit messages and changed files to right.

Please allow individual coloring of the entries in the branch window (accessible via CTRL+SHIFT+2). It should be possible to define both the text color and the background color separately for each branch as well as depending on the status "checked out" and "not checked out".

For this purpose, it would be an option to define classes in the settings, e.g. "warn" or "deploy", and then specify "warn" with regular status has red text color, "warn" with status "checked out" has white text color with red background. One can then assign a class to individual branches in the branch list.

This way, branches where a push results in subsequent actions (e.g. deploy to production) can be clearly highlighted ( and their potential impact...).

In the following situation, I have to repeat manual work. It could be automated:

• I have a feature branch and merged in develop at some point
• Merging in develop resulted in conflicts that I resolved
• Some time later, the feature branch is rebased on the then-latest develop
• The conflicts I've resolved when merging in develop now appear again and need to be resolved again.

Could the steps to resolve the merge conflicts be recorded and applied again on reabase?

looking for a way to auto add (by script) a group with many repos in it from the command line.
should i edit the repository-grouping.yml ?

Right now, open tabs of submodules are lost, when smartGit is closed. A option to keep them in the tabs until removed manually would be great.

See https://learn.microsoft.com/en-us/windows/win32/hidpi/setting-the-default-dpi-awareness-for-a-process

The current DpiAware/DpiAwareness level (which is probably 'unaware') leads to the GUI being bitmap scaled (and blurred) when the DPI changes e.g. when moved from a display with 125% display scale to one with 100% display scale.

Scaled to 125% display.

Scaled to 125% display then moved to a display with 100% display scale.

I regularly accidentally commit Local changes rather than Staged changes. Sure, it's user error, but after staging, I'm in the habit of just leaving the message and committing as you'd expect from most GIT GUIs. Especially as it usually defaults to "Staged Changes", it's hard always to remember to check which option has been chosen. 

An alternative fix would be to allow the option to always default to "Staged Changes".