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!
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
Enable Commit Signing for Background GenAI Messages (@ai, WIP)
For a Github repo that requires mandatory signed commits for PRs, the feature of background AI-generated commit messages (i.e. just putting "@ai" or "WIP" as message) is not usable as the final commit with the generated text is not signed.
Changes view: show changed file permissions
Current Behavior:
SmartGit’s Changes pane currently displays the unchanged file content twice when only a file’s permissions have changed. However, it does not show the actual mode difference (e.g., 100644 → 100755), making it difficult to audit permission changes without switching to external tools like the Git CLI.
Proposed Enhancement:
Display the exact file mode change inline in the Changes pane, such as:
File mode changed: 100644 → 100755
This should appear clearly above or alongside the diff view when no content changes are present.
Benefits:
- Improves visibility of non-content changes
- Helps developers catch unintended permission toggles
- Reduces reliance on Git CLI for metadata inspection
- Enhances trust and transparency in cross-platform workflows
Update the color contrast for search text
Currently the color contrast between the searched text and the background for added content is really bad and thus it took me 2 minutes just to find where the `next find` is pointing at. Please update this to take into account the background color so it "pops" at me and tell me where to look at.
Conflict Resolver: another view on conflicts
The only thing that i find often inconvenient in SmartGit - the way conflicts are displayed and handled in Conflict Resolver.
SmartGit view:
JetBrains GitClient view:
The later has much more clear (and less scaring :) LOL) picture of the conflicts.
Would be perfect if we are able to switch to yet another view on the conflicts that would be similar to the one on the second screenshot!
Thank you!
Customer support service by UserEcho
