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

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.

I'm running Windows 11 (ARM) using parallels on my M1 macbook pro. I can run smartgit on my mac which is great, but I can't install it on my windows VM, can you add support for windows arm as well?

Thanks

Options for add, create or clone Repository are only available on the Repository menu bar.

It would be useful to have this options on the Group context menu, too.

allow merge other remotes

Our team is working on a project where many files are changed and saved by tools.
Many of those files are identical to the versioned ones, except for EOLs.

We cannot change the EOL settings in Git, and SmartGit is showing tons of "Modified (EOLs only)" files.

It would be great to have the possibility to hide them in order to have a clean visualization of the files that needs for a (real) commit

It would be very handy if the Branches listed listed ORIG_HEAD in addition to HEAD for selection. So the user could quickly check ORIG_HEAD to see their previous state after commands like rebase. Thanks!

SmartGit should show an LFS indicator next to each file that *will be* committed with LFS, *before* the commit is done.

Ever so often, you bring in a new file type that should be handled with LFS. But without an indicator, it's not immediately obvious that you're committing such a file. Over and over, I accidentally put some 30 MB file into the normal repository, because it's some new executable or data file with a new extension, and I don't realize that this extension isn't already in .gitattributes. Then I realize the error, update .gitattributes, and going forward, this file type is now handled.

But the damage is done. I have half a dozen repositories that now have very large files on the normal Git side, which will never, ever leave the repositories.

SmartGit is hiding the LFS status too much. There should either be an indicator next to files that will be upload with LFS, or a column with the LFS status, that can be enabled.

The feature simply indicates whether the file name matches a mask in .gitattributes.

Please please please.

Thanks,

Per

When I have multiple staged files, but I select only some of them and press the button "Commit", I expect that the option "Local Changes" will be selected by default because I don't want to commit all staged files.

Sometimes, I forget to change the option, so SmartGit commits all staged files and it takes time to reset and re-commit.

At this time, the option "Staged changes" was selected automatically (https://smartgit.userecho.com/en/communities/1/topics/696-force-commit-dialog-to-always-select-staged-changes). It makes sense if the user selects nothing and only press the button "Commit".