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
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]).

+2

Log (Hg): allow to compare 2 repository states (like in the Git log)

Иван Анохин 8 years ago updated by Dave E 8 years ago 4

Let me compare two local branches by its commits and view diff between its files.

+2
Completed

Commit log should properly sort commits chronologically

Walt Destler 8 years ago updated by Marc Strapetz 8 years ago 5

When viewing a log with multiple branches, SmartGit often shows the commits non-chronologically. SmartGit should always show commits in chronological order whenever possible. (Obviously in some cases, such as when history is modified, it may be impossible to show commits in chronological order while maintaining proper parent-child ordering, but SmartGit seems to show commits non-chronologically even when not necessary.)


Here's an example where SmartGit is showing commits non-chronologically:


Image 64

+2

Support change detection and background fetch for submodules

Erik Sperling Johansen 8 years ago updated by Marc Strapetz 8 years ago 11

... regardless of whether a toplevel module is updated/fetched.


Optimally on a per-submodule basis, but an all-or-nothing switch is better than no support.


(topic description on 2017-03-10)

Answer
Marc Strapetz 8 years ago

I don't exactly understand the description -- the Journal for LibraryA will already show new commits for LibraryA. Can you please review your description and/or give more details?

+2

Add a button to make a pull in all submodules with their current branches

Christian Strahl 8 years ago 0

It would be nice to have a button to pull all submodules on the currently selected branch.

+2
Completed

Editing of global .gitconfig file

Benny Neugebauer 8 years ago updated by Thomas Singer 7 years ago 3

In the Repository Settings in one of my projects I have configured to sign commits with my GPG key:

Image 63

Now I don't want to use GPG anymore (that's why I deleted Gpg4win on my computer) but SmartGit always tries to sign my commits using "gpg2.exe".

I unchecked the "Sign all commits" option in my repository settings but if I add new repositories in SmartGit, then SmartGit still tries to sign them with GPG (even though the checkboxes are turned off).

What I am missing is a general setting within SmartGit, where I can configure GPG Signing on a global level.

+2

Option to ignore white spaces on merge operations

Seb D 8 years ago 0

As user I wish to be able to set an option during merge operations (including Git flow operations) to use the following "git merge" options:

-Xignore-space-change -Xignore-space-at-eol -Xignore-all-space

+2

Split "create pull request" title and description

Christian Ullrich 8 years ago 0

On GitHub (at least), a pull request has a separate title and description. An important difference between the two fields is that references to bugs or other PRs are detected only in the description.


SmartGit's "create pull request" dialog has a single large text field named "title and description". I think it might improve usability to either split this field in two, or to draw a line after the first paragraph (at the first newline) to indicate to the user where the title ends and the description begins. While a regular user of this feature will not make this mistake often, it is a bit annoying to both me and the repo owner I'm sending a pull request to if the whole description ends up in the title and no backlink appears in any bug I've referenced in the pull request text.


If there are hosting providers where this distinction does not exist, SmartGit can just merge the two fields' content again, if necessary (at the point the dialog appears, SmartGit should be aware where it will be sending the PR).

+2

Show branch name on the bottom status bar

tazxtreme369 8 years ago 0

When the most of my work is on a single repository, I don't need the repositories bar on the left hand side. But if I lose that bar, I won't know which branch I'm working on.

So, it's much cleaner if we show at least the branch name on the very spacious bottom status bar.