Especially with Mercurial that have native support for it.

SmartGit on Windows can access repositories located in the WSL file system, however there are a couple of issues:

• executable bits are not detected
• symlinks are not detected
• bad refresh performance ("git status")
• tricky re-configuration is required to use the Linux Git executable from within WSL

Useful information on how to access repositories on WSL with SmartGit in general can be found at topic 724.

Note: this topic is about running SmartGit installed on Windows and accessing repositories stored in WSL. If you want to run SmartGit directly in WSL, vote for topic 1408.

Please add SmartGit to winget. SmartGit will gain another "install surface" and developers better install experience. 

here is more info
https://www.howtogeek.com/674470/how-to-use-windows-10s-package-manager-winget/

When using the Git-Flow Full the branch overview of the log would be better readable if the master and the develop branch are visualized like in the picture from https://nvie.com/posts/a-successful-git-branching-model/ e.g first lane always master and second always develop and then the feature and hot-fixes lanes dynamically.

If master or develop are not present (either because they don't exist yet or they have only old commits), the lanes should still remain unoccupied.

master  devlop  feature X

    O          |            |

     |           |           O

When having a feature branch with multiple commits and rebasing onto the development branch, conflicts may be hard to understand:

- it's should be clear at which commit the conflict has occurred, which commits have already been processed and which commits are left to process

- maybe the involved commits for the conflict can somehow be visualized

(Optionally) call prepare-commit-msg hook to customize the default commit message

If Git writes URLs to stdout, they should be displayed as hyperlinks in the output window of SmartGit to open them in the default browser with a simple click.

This is especially useful when pushing new branches to remotes which response with an URL to open a new merge request, like GitLab does. Then you can just push a branch, click on the URL in the output window, and your merge request is opened in the browser.

Or as a second example, some remotes response with an URL to the new location of the repository if a repository was moved to another location.

This would greatly increase the clone speed for large repos that leverage LFS. More details can be found here: https://developer.atlassian.com/blog/2016/04/git-lfs-12-clone-faster/

This is the only part I don't manage inside of SmartGIT - I do those directly on the GitHub website, then once merged sync up again in SmartGIT and delete my local feature branch. :(