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 panel exposing the CLI (bash/cmd)

Thanos Politis 9 years ago updated by Thomas Singer 8 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 9 years ago updated by Thomas Singer 4 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 9 years ago updated by Thomas Singer 9 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 9 years ago 0
+2
Completed

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

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

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

Marc Strapetz 9 years ago updated 7 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

Check out Branch to new worktree

Bryce Schober 2 weeks ago updated by Thomas Singer 2 weeks ago 0

It would be really helpful to me if there were a simpler way to check out PRs and/or their branches to a worktree subdir of the current clone. IMO, this would be most discoverable as a right-click option nest to "Check Out...", as in "Check Out to new Worktree...". This right-click option could be made available on any branch selection, or even any commit selection context where "Check Out..." is offered.

Branches view Graph Improve Git commands
+1

Enable Commit Signing for Background GenAI Messages (@ai, WIP)

DRD 3 weeks ago updated by Daniel Siegl 3 weeks ago 1

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.

Commit dialog
+1

Repository View: Add Directory Tree Hierarchy option

Anthony Podkowa 4 weeks ago 0

Currently multiple repositories are organized by manually arranged groups on the "Local Repositories" tab. For my multi-repo workflow, I usually end up working with several clones clustered in directories that have all their dependencies together for an active task. This means that I might have multiple `foo` clones in various commit states on my disk. Because of this, it is often hard for me to tell which `foo` repo corresponds to which directory with the current SmartGit multirepo management system.

Rather than having things manually arranged into groups, it would be helpful to have a button that just sorts all the SmartGit-tracked repositories into collapsible file trees that match the directory structure on disk. This would be independent of the current manually user-defined groups which I can see as having distinct logistical value for some workflows.

Originally, I thought that this was how it worked, because on first install, that was how all the manual groups were configured. However, subsequent repository additions have required me manually dragging the files in the right place. This is kind of tedious, especially if I batch clone a bunch of repos from the command line and want to add them later into SmartGit.

If this proves too invasive to have independent options, I would be satisfied with an automated solution to sort the manual groups to match the directory structure. 


Loving SmartGit, by the way! Such a huge improvement over SourceTree!

GUI Repository Management