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

Add button for explicit big file diff

Iulian Onofrei 10 years ago • updated by Hyper Sonic 3 years ago • 13

I have a big file which couldn't get diffed in the main window. So I increased the size limit in the preferences file, but now, every time I select it, the diff process starts automatically and hands the background thread of the app (the UI is not blocked though). Even if I just want to commit it.


For binary files, there is a button named "Force Text", which works similar to my idea, which sounds like this:


The user changed the diff limit size:

- Y:

- the user selects a file whose size is bigger than the default one:

- Y: a "Force Diff" button appears

- the user presses the button: the diff process starts

- N: the diff process starts

- N:

- the user selects a file whose size is bigger than the default one:

- Y: the "File is too large to display." message appears (optionally, with a button that (creates? and) opens the preference file, or better yet, move those configurations in the UI)

- N: the diff process starts


Let me know if I was clear enough!


Thank you,

Iulian Onofrei

+2
Completed

Add panel exposing the CLI (bash/cmd)

Thanos Politis 10 years ago • updated by Thomas Singer 9 years ago • 2

Add a panel that will be exposing the OS CLI opened in the project's folder.

+2
Declined

Better support when using SmartGit for Git and Mercurial at the same time

Craig Caulfield 10 years ago • updated by Thomas Singer 5 years ago • 1

I use SmartGit for both Git and Mercurial, which is great: I have just one tool learn, and the same tool on Windows and on Mac. But, the commands and preferences for the two VCS are inconsistently implemented. For example:


The preference "Stash: Automatically save stash if Pull, Checkout, or Interactive Rebase fails because of local changes" works for Git but not Mercurial. Similarly, the Apply patch menu item uses the git apply command rather than the Mercurial import command even when pointing to a Mercurial repository.


SmartGit should be smart enough to know what sort of repository it is executing against and use the appropriate command, or tell us when that command hasn't been implemented.


Also, perhaps there needs to be separate preference tabs for Git- and Mercurial-specific preferences as there are some siginificant differences.

+2
Under review

Mercurial: support for creating and importing patches

Craig Caulfield 10 years ago • updated by Thomas Singer 10 years ago • 5

SmartGit allows you to create and apply a patches for Git, but not for Mercurial. Atlassian's SourceTree and the tool within Intellij IDEA have a context menu against log entries to create a patch from single or multiple commits.

+2

Enable editing git config

Robert Hannah 10 years ago • 0
+2
Completed

Log: option to hide branch-labels in graph, if unselected in Branches view [SG-8680]

Marc Strapetz 10 years ago • updated by Thomas Singer 9 years ago • 2
Missing Git feature
+2
Completed

Log: custom tools should work on Files (as in the main window)

Marc Strapetz 10 years ago • updated 8 years ago • 2

Tools configured in the Preferences should work on the Log's File view in a similar way as in the main window

+1

Temporarily maximize changes view

Bryce Schober 2 weeks ago • updated by Thomas Singer 2 weeks ago • 1

I would love to have the ability to "zoom in on" or temporarily maximize the changes view panel. This is a feature on VS Code side and bottom panels, and I find it really helpful to be able to toggle that quickly.

Changes view
+1

Commit message: Add option to enable auto-completion of file names for staged, unstaged, both

Hyper Sonic 3 weeks ago • 0

Currently, filename autocompletion in Commit message edit field works this way: when you press Ctrl+Space, a popup will show matching filenames for:

- if there are no staged files, all unstaged files (so all files with a modification, basically, although filters may affect this)

- if there is at least 1 staged file, all staged files

However, this is not compatible with my workflow, where I write a bullet point in my commit message for each file or group of files to explain their changes, *before* staging them. So on the contrary, I need autocompletion for unstaged files. Sometimes I also want to refer to a file even if it has already been staged, so ultimately I'd need autocompletion for all files.

To cater for all needs, SmartGit could provide flexible Commit message editing options (either in Preferences or in the small hamburger menu at the top-right of the commit message area, or both), to enable filename autocompletion for:

- all files

- unstaged files only

- staged files only

- disable autocompletion

(2 checkboxes for the 2 categories would be enough to produce the 4 combinations)

In addition, for people who like the current fallback system, an extra checkbox:

- if selected group (staged or unstaged) has no files, fall back to the other one (unstaged or staged, resp.)

This final option only makes sense if you chose staged files only or unstaged files only, so grey it out otherwise, I suppose.

Commit dialog