SmartGit doesn't support the GitHub PR templates, which would help improve the usability of the GitHub integration for organizations enforcing those kinds of standards, which includes a whole bunch of open-source projects.

this is a fairly popular OS, although not such a large user base

Windows 10 (Spring 2018 update) now directly provides its own built-in implementation of openssh. And it provides its own ssh-agent as a Windows Service for storing PassPhrases. There is no need for PuTTY and/or Pageant ever again!

Please support this asap in the SmartGit application!

When history is complicated and there a lot of branch paths drawn in the Log window, some paths are split with arrows. It allows to save space, but when you click on such an arrow, you have no idea where you have landed. Besides, if several arrows are pointing from a particular commit, and you are interested only in a particular one, you have to click on all of them in order to find out the necessary one. And BTW there is no easy way to "go back" in the Log window. It would be nice to see some preview information about a commit I am about to go to, when hovering an arrow. And it would be nice to have an ability to "go back".

Having a Conflict Solver open for a.txt, invoking the Conflict Solver a second time for a.txt should switch to the existing Conflict Solver window instead of opening a new one.

If having Conflict Solver windows open for a rebasing/merging/cherry-picking state, ask to close them when leaving this state.

It would be nice to select a folder and have SmartGit automatically add/remove repositories to match their existence in that directory. Cloning and deletion of repositories often happen outside of SmartGit.

SmartGit is useful for a quick visualization of status of your workspace, but if you forget to register a repo with SmartGit, you could potentially overlook any upstream or local changes.

Please add support for Julia syntax highlighting.

I'm doing development with a repository that has enormous submodules (e.g. linux, buildroot). In one of my environments (OS X, where I can't build but can easily view and edit) I haven't initialized the repositories, as it would suck down lots of bandwidth and disk space for no gain.

Unfortunately, when I look through the history, I can see that the submodules change, but there's no information as to what the changes are (the "Changes" panel just says "Submodule repository XXXX not found". Of course, the parent repository just changed the target commit in the submodule, and without the submodule present I couldn't see the files that change. However, it would be useful to know the commit SHA so I could look elsewhere and see just what changed.

So, request: when viewing a log for a repository with uninitialized submodules, the log should show the change in the commit SHA (even if the full information of the commit can't be seen).

AutoComplete similar as code editors do it, after entering one or two letters, would ease this process a lot.

Adding reviewer(s) to a Pull Request is error prone, as the entered name(s) must match the server login name exactly, including case.

Optionally the search should match any part of the login name, not only from the beginning, as some login names follow strange rules how they are derived from the real name.