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

Easier way to add worktrees and check out branches

Pavel Aronsky 3 years ago 0

Suppose I want to play with certain branch in the repo of which I already have a worktree on another  branch.

I try Repository->Add worktree  - oops, it tells me that I don't have that as a local branch...

Can this Just Work, please? All I want is get me a new working directory for certan branch, presto.

If this takes some actions under the hood, please do this for me.

* I cannot do check out on this branch, because this will stomp on my current working directory (where files are already open in my IDE ...)

* I don't want to go all the way from Repository->Clone.... enter the repo URL, then the branch....


+3

Perform file monitoring during Diffing

yccheok 3 years ago 0

Diff tool editor is a very handy tool for me to perform modifications on the spot, without a miss out anything.

However, I may sometimes switch between IDE and SmartGit's Diff tool editor.

When I perform an edit in IDE and forget to refresh the currently opened Diff tool editor, it will override all my IDE changes, if I press save in the Diff tool editor.

It will be great if the Diff tool comes with a file monitoring feature with the current logic

1. If it detects the file on disk has changed, and there is no change made in the Diff tool editor itself, it will silently reload the file.

2. If it detects the file on disk has changed, and there is a change made in the Diff tool editor, it will show a prompt, to ask the user whether he wants to reload.

Thank you.

+3

standard window: grouping branches by '/'

bernd schotanus 3 years ago updated by Thomas Singer 3 years ago 0

I have 1000 + branches. 

please re-use the branch grouping feature for the standard window. So I can see my branches in the 5 main categories again.

+3

Dark scrollbars in dark theme in Windows 11

Aleksei 3 years ago 0

In Windows 22H2 (latest) white scrollbars and menus are back. On the previous windows 22H1 version everything was fine

SmartGit 22.1

Image 728

+3

Standard window, My History view: optionally show tags in the graph

Marc Strapetz 3 years ago updated by pgoiffon 3 years ago 1

For those commits which are displayed (the graph roots are defined by your local branches), optionally also show tags, as the Log window does.

+3

Standard window: add option to display files as tree structure

Thomas Singer 3 years ago updated 3 years ago 0

Currently, files in the Local Files and History views are shown as list. The user only has the option whether to show it as name (path) or path/name. Depending on the directory structure the path part can get quite wide which might cause issues in the History view:

Image 714

Alternatively, there could be an option to show the files as tree-like list adding directory entries for each parent directory (without a way to collapse directories):

Image 715

This might require less horizontal space (but a lot more vertical space).

+3

Files view (Log): denote LFS-files

Marc Strapetz 3 years ago updated 3 years ago 0

Similar to topic #966, when selecting a Log commit, SmartGit should indicate for every file whether it is LFS-managed or not.

Note: for the general case, this may become a very expensive operation, because SmartGit will have to load all file blobs for the selected commit and check whether it is an LFS pointer or a regular file.

+3

Log, Filter: improve search for 'Content' in files performance

Maciej Andrzejewski 3 years ago updated by fourier 2 years ago 5

Better search for 'Content' in files.

This feature basicaly works but it is not usable in most of time so I have to fallback to command line and user 'git grep' to find what I need *in seconds*.

The way I use it now:

In the log screen I type searched string and check the 'Content' type.

The commits are being searched and now there are two problems:

First problem: The 'Files' view will not get filled/updated with searched data until whole repository search is completed. In big repositories that means I will never get the results and can wait for ages. Using 'git grep' I complete this part in seconds. It would be great to have *a button to stop searching* for commits and start analyzing the 'Files' output.

+3

Progress indicator for git-lfs

jimkeir 3 years ago 0

When uploading large files to a remote repo using git-lfs, it would be very useful to be able to see the progress which I believe is available from the git-lfs process. I can see lots of network activity so I know it's busy, but I can't tell whether I should wait a moment, go for coffee, watch a movie or buy a second computer to work on in the meantime.

For that matter, "upload LFS files in the background" would be welcome, too.

+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.