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!
Add panel exposing the CLI (bash/cmd)
Add a panel that will be exposing the OS CLI opened in the project's folder.
Better support when using SmartGit for Git and Mercurial at the same time
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.
Mercurial: support for creating and importing patches
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.
Log: custom tools should work on Files (as in the main window)
Tools configured in the Preferences should work on the Log's File view in a similar way as in the main window
Temporarily maximize changes view
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.
Commit message: Add option to enable auto-completion of file names for staged, unstaged, both
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.
Move repositories into group via commandline arguments
I would like to have a commandline option available for smartgit.exe which enables me to move a repository into a 'Group' in the Repositories window.
At the moment this is a manual activity which is taking too much time since, in our situation, the number of involved repositories is increasing rapidly over 30.
When this commandline option is available we can use scripting to move these repositories to the correct group which saves lots of time and reduces errors.
Customer support service by UserEcho