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!

+1

"Branches" view in log: Auto-select filter

Stefan 8 years ago 0

In the log window, I tend to select only have a few branches selected (related to current work) to avoid cluttering log history.

I would like to have this dynamically done via a filter.


For instance, I create branch "ft-issue123", then sub-branches off it like "ft-issue123-fileFixes", "ft-issue123-dbIntegration" etc.

I would then like be able to auto-select branches matching e.g. "issue123", so I automatically get log updated when there are new branches matching the filter.

+1
Completed

add branch ref to Tools Arguments

friuns 8 years ago updated 8 years ago 2


there is commit ID but no branch id, branch id would help a lot to make more advanced custom commands!

+1
Completed

When journal runs into a conflict, give the opportunity to resolve and continue

Florian Kaufmann 8 years ago updated by Christopher Kline 8 years ago 2

When rewriting history via the journal (i.e. interactive rebase) runs into a conflict, it currently completely aborts (seems like "rebase --abort"). Like in native rebase --interactive I would like the opportunity to choose between 1) resolve the conflict and continue and 2) abort the interactive rebase.

+1
Completed

Remove "annotated tag" checkbox

omegatron 8 years ago updated by Thomas Singer 8 years ago 1

If you check "annotated tag", you must fill out the Message field in order to press Ok.


If you do not check "annotated tag", then the Message field is grayed out.


So the checkbox is redundant with the message box. If you fill in a message, it should automatically become an annotated tag, and if you don't, then it shouldn't.

+1
Completed

Allow to selectively enable the submodules that will be acted on.

Kuba Ober 8 years ago updated by Thomas Singer 8 years ago 1

Large repositories, such as Qt's git://code.qt.io/qt/qt5.git contain multiple submodules. The normal workflow doesn't necessarily include all of those submodules. Allow the user to selectively enable only the submodules she desires.

+1
Completed

Force push with lease

charlesgael djedai 8 years ago updated by Thomas Singer 8 years ago 1

By default the application when rewriting the history uses git push --force (in the case of GIT).

It woulf be good that it rather (or at lease give the choice) uses --force-with-lease which is more secure.

+1
Completed

View tags in groups

Sync 8 years ago updated by Thomas Singer 8 years ago 1

Currently, Branches with the same name before a forward slash are grouped together, but Tags are not.


Source Tree does the grouping for both Branches and Tags, plus they have a nice folder icon for it for a more pleasant UI experience.

+1
Duplicate

Compare Stash with working tree

David 8 years ago updated by Thomas Singer 8 years ago 1

Quickly see what the stash would change of applied to the working copy, summary of change files woudl be good, this woudl allow you to dop an irrelavant stash quickly and easily

+1

Allow svn branch names with slash symbol

dmitry andreev dev 8 years ago updated 8 years ago 2

Right now I can't see any branch from remote SVN server if the branch name contains '/'. For example 'feature/15232_pathfinding' is displayed as 'feature' and I'm unable to check it out. Furthermore I cannot create a brach with '/' in it. Tortoise SVN allows to operate with such names so it would be great if SmartGit would also understand them.

+1

When working with groups, the UI should only be disabled for repositories that are executing actions

gj roelofs 8 years ago updated by Thomas Singer 8 years ago 1

Currently, when working with groups of repositories whenever one repository is being updated/pulled/pushed, UI (logging etc) is disabled for all other repositories.