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!

+4

Custom ordering of groups and repositories

Daniel Filipe 8 years ago updated by Thomas Singer 8 years ago 1

Alphabetical ordering doesn't really scale well when you work with a lot of repositories. I'd like to be able to custom order (either via drag-and-drop or arrow buttons) my groups and repositories so I can shift them around as priorities change without needing to put them in "A Most Important Group!"

+4
Completed

Journal: option to hide common commits [SG-10558]

Ionut Morariu 8 years ago updated by Marc Strapetz 8 years ago 14

If i had one commit unpushed i wanted to see it down below in the outgoing section. The problem here is that there is no option here to filter only the unpushed items.

+4

Diff tool should insert code difference, for example, when SHIFT key is pressed

Андрей Шенец 9 years ago updated by k h 8 years ago 5

Right now when you compare changes in two panel diff tool, or three panel diff tool you can got case when diff tool allows you only to replace code. It can happen when in two branches the same line of code has been changed and you are trying to merge these files.

It would be great to have possibility to force diff tool to insert diff line if SHIFT key is pressed.


Image 24

+4

When receiving the message "the following untracked working tree files...", allow the user a choice.

Thomas Hansen 9 years ago 0

When switching to/from a branch where new files are added sometimes files are left behind (soapui project xml for example), when switching back to the branch with the new files you'll often get the warning "The following untracked working tree files would be overwritten by checkout", and a list.


It would be nice to have an option added to this dialog to basically say "ok, overwrite them". Instead of having to look them up 1 by 1, and manually deleting them before trying to switch to the branch a second time.

+4

Show details for annotated tags [SG-8209]

Marc Strapetz 9 years ago updated by Thomas Singer 7 years ago 2
Missing Git feature
+4

OS X: use native keystore instead of own password manager [SG-7921]

Marc Strapetz 9 years ago updated 9 years ago 0
+3

Add support for rebasing stacked branches

andrewleech 3 weeks ago updated 2 weeks ago 3

Hello,

Could an option be added to include the --update-refs arguement for rebase operations? Either in drop down menu during rebase or just a checkbox in preferences / advanced settings would be fine from my perspective.


I quite often work on large features that then get split into multiple branches stacked on top of each other.

I generally work on projects using a rebase strategy rather than merging branches into main, so I end up wanting to rebase the stacked branches onto the head of main for testing / submission.

Currently I end up needing to drag/drop the whole branch onto main to rebase it as just the lastest branch name, then manually drag the intermediate branch labels up to where they're supposed to be in the stack which is quite tedious and error prone. 

Alternatively I drop to the terminal to run the rebase there with --update-refs and it moves all the intermediate branches for me along with the rebase.

Improve Git commands Missing Git feature
+3

Add ability for graph squash context menu to work on non-contiguous commits

David Rees 7 months ago 0

Add ability for Squash context menu in log view to work for non-consecutive commits. Currently it only works for consecutive commits. If non-consecutive commits are chosen then smartgit would trigger a interactive rebase that does the following:

- reorder selected commits so they are consecutive

- then squash them

If there is an merge issue then smartgit drops into interactive rebase resolve step so use can resolve (or cancel).

Log window Standard window
+3

Allow double-click to stage in Log and Working Tree windows

David Rees 7 months ago updated by Daniel Siegl 7 months ago 2

Standard Window has the option for double-clicking of a local file to stage or unstage changes for that file. Please add that same option for Log and Working Tree windows. Thanks!

Log window Working Tree window
+3

Allow custom colors for red/yellow/green messages in the Output pane

lshort 8 months ago updated by Daniel Siegl 8 months ago 1

Those of us who are colorblind would find it useful to be able to set custom colors for "red", "yellow", and "green" messages in the Output log.  With tiny icons on a 4K monitor, it is easy to overlook a failed operation.