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!
Latest RC introduced a dark color scheme.
This is good but sadly when working at night the side panes are still white and occurs lot of eye strain.
I would love to see a color switch of the whole interface including panes, menus, button bar...
Purple, green, pink, orange, thin/thick lines .... what branch is which?
It would be useful to have a mean to determine the branch associated to each line.
Also, hoovering the mouse cursor over a line would show the branch name and the last 'x' GIT operations made against that branch.
Topics, related to further improvements:
- Branch colors configurable based on keywords for branch names: https://smartgit.userecho.com/topics/723
In a typical workflow, I develop on a "Sprint" branch, merge code into a "Test" branch, followed by a merge into a "Production" branch. However, the ordering of commits in SmartGit can make it challenging to see exactly where my Test/Prod branches were merged. Further, it can be challenging to see if a certain commit has made it live.
I have photoshopped a sample (below) of my log to describe the desired end-case. In this example, the "Production" branch has been pinned to the left, and was randomly chosen to be yellow. The Test branch has been pinned second to the left in red. The Sprint branch has been pinned as the third branch is in Green.
All other commits on un-pinned branches revert to the display logic that currently exists in Smart-Git
Applying a stash may fail due to conflicts. It would be helpful to be able to view what is in a stash and selectively apply a subset of the files.
There's a large number of very useful customizations that can be made via smartgit.properties.
- It's very hard to know what all the available options are (they're scattered across various web pages, and these docs are sometimes updated sporadically or slowly)
- There's no way to know when a new setting become available unless it happens to be mentioned in the release notes (which it often is not), and you are diligent enough to read every release note
- When properties are removed from the application, they can remain (non-functional) in your smartgit.properties
- If the setting is misspelled in smartgit.properties, there's no obvious indication of a problem
What I would like is for a UI dialog (perhaps "Customize") to list, document (via a tooltip) and allow editing of every supported setting that can be configured in smartgit.properties.
I'm fine with the editing being raw text like it is now. I just want everything in one place.
A bonus would be a column listing what version the setting was introduced in, so it's easy to see when new settings have been added.
Allows to see the diff between the working tree and the selected commit.
See also: https://smartgit.userecho.com/topics/655
Refresh: recognize Rename (as "git status" does), instead of showing Missing and Untracked now [SG-2361]
Allow me rename file like git mv command. It may be context menu or auto recognition of file changes.
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.
Customer support service by UserEcho