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!
File Manager integration
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.
Better distinguishable icons for "untracked" and "added" states
The new icons in SmartGit 26 for "untracked" and "added" states are very similar in color and shape, which makes it hard to distinguish between those states. This is especially an issue in the working tree view, where both icons are mixed.
It would be better if the untracked icon had a different color than green (it previously was blue in SmartGit 25), since this would help to see the state at once without paying attention to the exact shade of green or the additional white pixels between the star and plus icon.

Support Markdown in commit messages [SG-16156]
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.
Change tag color
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?

22.1 Preview: Keep old style of commits behind/ahead
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:

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.
This should be the default way of interacting with git repositories
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.
.gitignore/.gitattributes: provide some smart editor
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).
Refresh (WT): optionally deep-scan into ignored directories [SG-8516]
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
Ability to view size on disk difference of modified files
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:


Customer support service by UserEcho