Share your ideas on how to improve SmartGit!


This is no support platform! To report bugs or request support, please contact us directly. If in doubt ask us.


First search for a similar request and add your votes or comments there.


Take the time to describe your request as precisely as possible, so users will understand what you want. Please note that we appreciate your time and input, but we don't give any guarantees that a certain feature will be implemented. Usually, a minimum requirement is a sufficient number of votes. Hence, please don't comment like "when will this be implemented", but vote instead.

Follow the stackoverflow.com writing guidelines.

Thank you for your help!

+3

Add support for "multiline" code review comments

nassim mahmoud47 3 years ago 0

Github and Gitlab added support for multiline comments. It would be nice if one could make a comment that applies to multiple lines directly from SmartGit client.

+3

Git: SHA-256 support

Marc Strapetz 3 years ago updated 3 years ago 0

Support for SHA-256 repositories and operations (Git --object-format=sha256 option)

+3

Long file name support under windows 10 for SmartGit

heiko masiero 3 years ago updated 3 years ago 1

Path length longer than 260 characters result in Missing Files under Windows 10.

There is an Solution in Windows 10 Version 1607 and later

"Enable Long Paths"

see Maximum Path Length Limitation - Win32 apps | Microsoft Docs

Request for SmartGit supports these long paths

+3

Allow to activate/deactivate multiple selected submodules

Marco Esposito 3 years ago updated by Marc Strapetz 7 months ago 4

When operating on a large repository with multiple submodules, it is possible to manually initialize/deactivate single submodules. However, this can be a very tedious operation, since each single repository must be selected, right clicked on, and finally inited/deactivated.

Please allow to select multiple submodules, right click, and initialize/deactivate them altogether.

+3

Output view: don't limit lines of current command

Thomas Singer 3 years ago 0

But instead, maybe, auto-remove older commands.

+3

Allow configurable default selected branches in the log view

bernd schotanus 4 years ago updated 4 years ago 3

in 99% percent of the cases I'm interested only  in the master branch + the ~6 latest 'stable/*' branches when viewing the log.

We have many repositories following this scheme.

It would be nice if we could have a default branch selection configurable as a default for all repositories something like
master

stable/*

+3

"Discard to Stash": option to show dialog for entering name

Sync 4 years ago 0

Currently, "Discard to stash" will directly create the stash, and users will need to go to the Stash tree to rename the entry.  

It would be nice if a textbox would appear after "Discard to stash" is clicked, similar to how "Commit" button works.  If this is not desired for the general public, perhaps make it an advanced option.

+3

Favorites branches

Anatoly 4 years ago updated 4 years ago 1

I propose to make it possible to add branches to favorites or pin them, since there are a lot of branches, but there are a couple of them that are most frequently used. Thank you.

+3

Multi-repository Support: Simultaneous Git-Flow Transactions

Sean McNeill 4 years ago updated by Marc Strapetz 4 years ago 2

I have many repositories, organized into groups. For example Project A will consists of four or five different repositories. When I do  a hotfix, I do it to all of the repositories used by that project, so they all have a 1.70.10 tag that I can build from, even if only one of the repositories changes. 

So, it would be nice to perform operations like "finish hotfix" on multiple repositories (perhaps all in a Group) all at the same time, and have them all working on the git flow operations simultaneously. Right now I do them one at a time and it can be tedious. I have external scripts to accomplish this but it would be nice to be able to do it right from Smartgit.

+3

Conflict Resolver: show diverged commits (with their messages)

Will Hains 4 years ago updated by Thomas Singer 4 years ago 1

I use and love the “Conflict Resolver” window every day. It is extremely useful to have a 3-way diff like that. I love the “Base Changes” window as well.

But sometimes it is difficult to understand why the change in either side was made. My suggestion is to show, at the top of the left and right editors, a list of the commits since the common root. The abbreviated SHA1 (perhaps linked, so that clicking opens that commit in the Log view), author, date, and the first line of the message.