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 precise as possible, so we (Syntevo) and other users will understand what you want. A plain request "SmartGit should look cool" is too vague because we don't know what we should change, and hence will not be approved by us.

Thank you for your help!


Azure DevOps integration (like GitHub, Bitbucket)

hrant 3 years ago updated by Hrvoje Hudo 6 months ago 6

Visual Studio Team Services is a popular and common tool among .net developers.

Although SmartGit can clone / pull ... from the Git repo, it is lacking proper integration similar to Github.

For example it would be desired to be able to do Pull Requests from within SmartGit, rather than jumping to another tool.


GUI for Git lfs

smartgit 3 years ago updated by Thomas Singer 1 year ago 12

Git lfs is a great, additional feature when using Git for situations, where blobs need to versioned, too. I would love to see a nice GUI integration of Git "large file storage".


Show all modified line endings in diff viewers

ubruhin 3 years ago updated by Thomas Singer 2 years ago 13

Until now, modified EOLs are nearly not visible in SmartGit. There's only a label which shows for example "EOL: Unix vx. Windows", but it's very easy to overlook it because the diff itself shows no changes.

In addition, if a file has different EOLs, SmartGit just says "EOL: Mixed" but does not show which line has which line ending. And staging/discarding them line by line is also not possible.

In my opinion, differences in EOLs should be visible in diff viewers with some kind of symbol on each line, like "git diff" does. So the user can see which line has which line ending, and can even fix them by staging or discarding line by line, just like all other changes.

This feature may be useless on Windows with "core.autocrlf=true", but on other operating systems or with "core.autocrlf=false" this would be extremely helpful because one can see and fix introduced EOL changes.


Log: show index/working tree (as "virtual" commits on top of HEAD) [SG-11650]

Marc Strapetz 3 years ago updated by Pierre Goiffon 2 years ago 10

Allow to collapse unchanged blocks of code in diff view

Krzysztof Kot 3 years ago updated by Thomas Singer 2 years ago 23

Tool that I'm currently using allow this and it saves me a lot of scrolling so for me it would be nice feature.


Import/Export SmartGit settings

iglvzx 3 years ago updated by T.M 4 months ago 3

I would love the ability to export my SmartGit settings into a single config file so then I can easily & quickly import my settings later when reinstalling or installing on a new system.

I am aware you can sync/copy settings from one SmartGit installation to another by copying over the various .XML files in the SmartGit settings folder, but this can be messy and cause problems if not done correctly.


Git: Interactive Rebase

Robert Pösel 3 years ago updated by Thomas Singer 2 years ago 11

Support interactive rebase directly from SmartGit.


Replace "Commit" button with "Continue Rebase", "Discard" with "Abort Rebase", etc. [SG-10349]

omegatron 3 years ago updated by Marc Strapetz 3 years ago 6

To continue rebase after fixing a conflict, you have to press Commit.

To abort it, you select the project and press Discard?

These aren't very clear actions. It would be better if the buttons actually changed their names while in the middle of a rebase.


Prune merged local branches (e.g when fetching)

Theodoros Antoniou 3 years ago updated by Thomas Singer 5 days ago 14

When fetching from a remote, allow the choice to prune (delete) any local branches, which are tracking a remote branch that has been merged.

This is quite a common task, especially if you work in a team that uses a lot of feature branches and Pull Requests. Stackoverflow related question

P.s: This is a feature available in SourceTree.


Log: integrate into main window

Marc Strapetz 3 years ago updated 10 months ago 35

To unite Log and "Working Tree" window, there are two options: add Log functionality to the "Working Tree" window or add working tree functionality to the Log window. For conceptual and technical reasons, we opted for the latter option

Instead of having a separate Log window, this should be part of the main window in order to have all functionality of SmartGit be available in a single window.

This would mean to add all views of the Log to the main window, duplicating a couple of them with slightly different meaning, e.g. the Changes view in the Log is purely read-only, but can show comments - the one in the repository window can be used to stage/unstage; the Files view in the Log does not allow any of the main window's commands; the Branches view in the Log allows toggling anchor commits for the Commits graph and shows additional items, e.g. recyclable commits. It would be a horrible amount of work and still would require stand-alone Log windows, e.g. for file or subdirectory logs.