Exactly what https://smartgit.userecho.com/communities/1/topics/1216-output-parse-or-ignore-color-sequences-in-hook-output says, but the other solution. Meaning, it would be great if SmartGit would parse the ANSI sequences in order to add colors to the output, so it's easier to understand (e.g. errors in) hooks outputs.

This would be especially helpful in the Log window.

Here is some inspiration from GitHub's UI:

Since our IT installed a new version of SmartGit (22.1.1 #19231) I get a sub-menue to resolve merge conflicts instead of a popup window.

This is not the problem but in the former window there were always the two possible source branch names. In the new menu there is just "Take Ours" and "Take Theirs" and I have no idea which I have to take to get the right file!

Is there a way to display the source branch names or to get back to the former popup window? The current solution is really a problem for me. By the way: our source code files are binary and usually stored with LFS option. So I even cannot compare them by looking to the file content.

Note: This is unrelated to the existing requests for different icon for file statuses.

The filter buttons in the file list which allow a user to determine whether or not the list should include unchanged files, non-version controlled, ignored files, etc. are currently very similar, visually, and it's hard to tell at a glance what each of them does.

These are the icons I refer to:

In fact, it's easier to try and memorize the position of the buttons, rather than what icon matches which button. The worst offender by far is the "assume unchanged" icon which has a tiny icon highlighted pink and is only three pixels different from another icon!

At present these icons display a file icon with a small glyph to differentiate them. I think it would be better if the glyphs were much larger and covered the file, rather than a small item in the corner.

I have created a mockup using aha-soft's small application icons (available under a creative commons attribution share-alike license) altered slightly. The design goals for this was to have icons distinct by shape and colour.

I'd be happy to discuss alternative solutions and also happy to share icon files if you'd just like to use these - though you would need an attribution notice somewhere in the software.

When I select the found commit the 'Files' view now contains all the files that have been changed in that commit. If the commit contains dozens of changed files I have to manually check each file and manully search for phrase I have been searching in the first place. I understand that 'Files' view always shows the files in the commit so maybe add posibility in the 'File Filter' search box to additionaly only filter files based on typed content?

There's are grayed out Commit button on the right side, but none in the toolbar next to Push like in the Working Tree Window. Also there does not seem to be a way to configure the toolbar, at least it doesn't have a context menu.

When a tracked branch has been deleted on the remote, the Branches list shows a red checkmark after the name. But if the branch names are longer and/or use the features/hotfix/etc method, then the red checkmark is often cut off. Makring the Branches window wider just cuts into the Changes, File, and Graph.

While I know I can hover over branch, it would nice if there was an option to either put an indicator at the front of the branch name, or change the branch name's color as in RFE at https://smartgit.userecho.com/en/communities/1/topics/1221-log-graph-mark-branches-for-which-the-tracking-ones-were-deleted-with-red-as-in-branches-view

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).

When doing code reviews for pull requests, it would be very useful to automatically select destination branch from the source branch from which the branch was originally created. The current behavior is that the last used destination branch is populated by default.

It is very common that we forget to change the last used branch when we are doing changes in master and release branches. The result is that we create a pull request into wrong destination branch....

I have a license for SmartGit from my company and recently I switched to a M1 Max MacBook Pro. However, due to my work, I have to run a Linux virtual machine and use SmartGit inside that virtual machine. Because the processor architecture is arm64/aarch64, there is no SmartGit for Linux arm64/aarch64. 

I am aware that SmartGit for Apple silicon is available but I would need to use it on Linux.

Thank you.