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!

+6

File Manager integration

Thambaru Wijesekara 10 years ago updated by Ivan 7 years ago 2

SmartGit doesn't integrate with Windows Explorer or Nautilus in Ubuntu yet like other Git clients (Tortoise Git, Rabbit). It'd be great to go for that since we have to load all projects at once just to commit one project. I'm working on multiple projects at once so it's very inconvenient to close and Add them again to SmartGit.

+5
Started

Support Markdown in commit messages [SG-16156]

Sync 3 years ago updated by Marc Strapetz 3 years ago 4

It would be nice if the [Commit] window would display commit messages in Markdown. 

Even if it's an opt-in advanced option, I would be happy.

+5

Change tag color

silkfire 3 years ago updated by Giorgio Croci Candiani 3 years ago 3

In the latest version (22.1), the color of tags was changed to gray. I'd like to revert it to the previous yellow which I think has better contrast and is more intuitive to me. I couldn't find a way to change this in the settings, is there some other way of customizing it? Maybe through a .theme file?

Image 735

+5

22.1 Preview: Keep old style of commits behind/ahead

Fredrik Blomqvist 4 years ago updated by Roland Schmitt 3 years ago 6

I've been a user of SmartGit for 10+ years and really like the Working Tree window. I don't find the new Standard window anywhere near as good, but that's fine since the Working Tree window is staying.

However, I noticed the style for showing how many commits a branch is behind/ahead changed into some gray subtle numbers. I like the old style a lot better since it's just visually clearer

Example:

Image 717

Same goes for branches that are missing their tracking branch and so forth. The old/current stable theme is superior imo. Not sure what else I can do other than beg you to keep it or make this new style an option or theme.

+5
Thanks

This should be the default way of interacting with git repositories

Iulian Onofrei 5 years ago updated by Marc Strapetz 5 years ago 1

I can't imagine life without SmartGit, and I urge people to use it whenever I find the opportunity. I find it especially useful for beginner git users, but who want/need to do advanced stuff like rebasing. The SmartGit's Log window is a lot more easier to use than the `git` command directly, the diff is the best in the world, and the ease of use is on top of other programs that I've tried.

+5

.gitignore/.gitattributes: provide some smart editor

Thomas Singer 5 years ago 0

For each selected a line (entry) it could show (in a separate view) the matching files. It also could highlight lines that are obsolete (not matched by any file).

+5

Refresh (WT): optionally deep-scan into ignored directories [SG-8516]

Marc Strapetz 6 years ago updated by Charles 6 years ago 1

Latest SmartGit will not show files in ignored folders, even though ignored files are shown (Ctrl+3). This makes it impossible to stage such files. Command line git will optionally display such files when invoking git status --ignored --untracked

+5

Ability to view size on disk difference of modified files

Danny Lake 6 years ago updated by Daniel Siegl 2 years ago 2

We are coming from a centralized source control repository and adopting Git. One thing we loved about our old tool (SourceGear Vault) was that for our modified files, it showed us the difference of the modified file's size on disk compared to the current version in source control. This was helpful for us and provided some context on the size of the change we made to each file. 


For example if one file has +10kb of changes, then we know that is a significant change and should be reviewed closely before committing, where as a +1 byte delta would tell us it was a trivial/minor change to the file.


Having the ability to also sort on the file size delta was helpful to get the most significant changes (largest deltas) grouped together before committing, helping us see the biggest changes in one spot rather than sorted by filename or by folder. Sometimes we'd catch a 'console.log' statement in a file when sorting by size as well, as that change would be around +18 bytes to a file, which is easier to detect and remove before committing when sorting changes by size.

See screenshots for where this would be great in SmartGit, and how it is displayed in SourceGear Vault: 

Image 541

Image 543

+5

Log Graph: mark branches for which the tracking ones were deleted with red, as in Branches view

Iulian Onofrei 6 years ago updated by Marc Strapetz 6 years ago 0

When the tracking branch gets deletes, the local one shows up like this in the Branches pane:

Image 536

and like this in the Graph pane (Log window):

Image 537

It would help a lot if they were marked the same in both places.

I'd want this because the branches in the Branches pane are not sorted by date, and are also grouped. So I have to exact each and one of my groups to find out which local branches to delete.

Whereas in the Graph pane, the branches at the top get merged, and as such, their local counterparts need to be deleted.