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!

+2

Journal: show branch labels for all of the branches included in the current branch

George Bessonov 8 years ago 0

E.g. if any branch heads to any commit included in the branch currently checked out, show it's label instead of showing just the branch currently checked out local and remote labels.

+2

When starting a GitFlow Bug it should automatically stash/unstash instead of immediately failing

Scott Richmond 8 years ago updated 8 years ago 2

It is extremely common that one starts a feature or bug prior to actually starting the GitFlow process. This means there are often unstaged changes before starting a GitFlow bug/feature. When you do this, it will fail as there are uncommitted changes when it needs to change branch/make a branch/etc.


Unfortunately SmartGit isn't automatically stashing/unstashing in response to this. Which makes using GitFlwo very frustrating.


It should be no issue to stash all changes, perform the GitFlow process, then unstash.

+2
Started

Better detection for gerrit repositories

Adrien Béraud 8 years ago updated by Marc Strapetz 5 years ago 3

I use Gerrit with Smartgit for many repos but Gerrit was never detected by Smartgit despite claimed support.


Documentation says:

SmartGit will detect a remote as being connected to Gerrit, if:

  • .git/hooks/commit-msg exists; and
  • there is only one remote overall or it's the only remote connecting to port 29418 (default Gerrit SSH port)

The second condition is clearly too restrictive. Repos I work with use port 29420 so I'm doomed to never see them detected with current detection method.

+2
Completed

Abililty to have GitFlow icon in the log window

Pierre Goiffon 8 years ago updated by Thomas Singer 6 years ago 2

For now the GitFlow button can't be added in the log window toolbar... I miss it lots of time when preparing / finishing a release !

+2

Add "Expand/Collapse All" feature in Branches Tab

Sync 8 years ago 0

Add the ability to expand or collapse everything in the Branches Tab. This will recursively go through every branch and tag, and expand (or collapse) those that are grouped together.

+2

Submodule options should be available in right-click menu

Bryce Schober 8 years ago updated 8 years ago 1

It seems to me that the submodule options found in the Remote > Submodule menu should also be available when right-clicking on the root of a specific submodule.

+2
Completed

Git-Flow Finish Feature: support mixture of rebase and merge

George Bessonov 8 years ago updated by Marc Strapetz 6 years ago 5
+2

Possibility to show the "Log" from left to right

werbemist 8 years ago updated by Alexander Zhezherun 8 years ago 15

Reduced branch graph, more compact/less information as the current Log. See the images for example here:
https://git-scm.com/book/de/v1/Git-Branching-Einfaches-Branching-und-Merging

+2
Completed

Make keyboard shortcuts available for all the different windows

Iulian Onofrei 8 years ago updated by Thomas Singer 5 years ago 1

If you set a keyboard shortcut for, say, "Next Change", in the "Index Editor" window will not work. The "Customize..." menu also points to this behavior by printing "Changes | Next Change" instead of simply "Next Change"

+2

When creating a new Feature (Gitflow), show me what last used names were

Brice P. 8 years ago 0

The purpose is to easily maintain a counter, like :

Feature-2017-05_my_feature

Then, when I'll create a new feature, whether this one has been closed or not, I'll know I'll have to name it Feature-2017-06_my_new_feature.

The same goes for releases (I name them Release-[number]) and hotfixes (Hotfix-[release_number]-[hotfix_number]).