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!

Push-To: retain last remote selection
It would be nice if the previously-selected remote repo (multiple) in the Push To dialog can be retained, so that we don't have to re-select each time until we really need to select a different repo.

Export Modified Files Retaining Folder Structure
I'd like the ability to export the selected modified files to a directory and maintain the file structure of the modified files. i.e. if I have selected two files, one in an EXP directory and one in an IMP directory, then I'd expect and IMP and EXP directory to be created with the files in the correct folders.
Ideally, also like the ability to do this from the main window showing changed files, but also from the log window when comparing two commits or looking at a single commit.
This is similar to the functionality in Tortoise GIT using the right-click "Export Selection To" option.

Add Remote: better default name of remote from URL
If a remote from GitHub is added always the last part of the url, which is the repository name, is used. If you want to add another fork to modify the branch as maintainer of the forked repository I always need to change the name.
E.g. for GitHub it would be better to not take the last part, e.g. instead of https://github.com/Spacetown/gcovr it would be better to take https://github.com/Spacetown/gcovr or the last two parts.

Add message explaining why Standard view cannot be selected without commercial license
Currently, when not using a Commercial license, the Standard view is greyed out and cannot be selected on both onboarding Style selection and later selection in Preferences.
However, there is no message indicating that this is unavailable due to not having Commercial license. This may be disturbing to new users, especially as in the onboarding process, it's written "Recommended for new users" just below the Standard view description!
Stack Overflow question with image:

Configurable "open in" menu
The context menu for repositories includes options to "Open In" explorer, git-shell, terminal, and a few more. I'd love to be able to configure that list for my preferred tools, like
- Open in Windows Terminal (my settings don't match what I get when I pick "Open in terminal" or "Open in Powershell"),
- Open in VS Code
- Open in TotalCommander
I see several other feature requests with specific new menu items but it's pretty long as it is - making it configurable would simplify the menu and make it more flexible for everyone.

Exclude log filter
Our automation server commits a nightly build with a commit message "Nightly Build...". It would be nice to exclude these commits from the graph view using a filter either in the UI or git config file.

Hi,
I just did a test based on: https://github.com/danielsiegl/CommitFilterTest
And I can reproduce that this is working with 23.1.x and with 24.1.x - but you need to select "Message" only.

Standard Window: support releases for the Feature Flow (similar to Git Flow Releases)
Currently the standard window supports everything needed to work with feature branches using git flow.
What about the other types of branches?
Personally, I am only missing "Start release" and "Finish release", but others might need hotfixes or support branches as well.
Having to switch to the log window to create a release feels wrong ;-)
Since most people will (hopefully) create releases far less frequently than features, I think it would suffice to put those commands into the "Branch" drop down menu - maybe even under a sub-menu "Git Flow".

Add meta-information (note, tag, flag) to repository or group
It would be nice to have the ability to add a personal note, tag, flag, etc. to some repository or a whole group (e.g. mark repository with a "<red flag>", as with some E-Mail clients)

Could I please have hotkeys on the underlined functionality below?
Could get 90% of the way there by supporting a hotkey for "Amend Last Commit", "Commit" and "Commit & Push". The others are a bonus.
I'm on Mac.
Customer support service by UserEcho