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!
Blame: UTF-8 support [SG-10461]
My file is UTF-8. In the Log window the Chinese characters show up normal, but
in the blame window the Chinese characters show up garbled.
Add the ability to say warn/block before pushing to a remote
I have remotes, which I have Write access to, that I never want to push to using SmartGit. Allow me to configure SmartGit to restrict somehow pushing to those remotes.
This does not need to apply to the command line as well.
preference to ignore or set fixed line endings and file permissions
I develop on Linux and windows the same code, so I don't really care what line endings are used where.
I do prefer to have Unix line endings everywhere because in Windows, my editor knows what to do about them but in Linux, it is better to get rid of Windows line endings.
So, I'd like to have a preference to enable one type of line ending that would be carried away to all copies of my code.
Even better option would be to have a logic that would somehow detect the line endings on the origin, and convert as I want it on local, automatically.
For example, if I create a repo and make some source files on Linux, then push it to GitHub for example, then clone it on Windows, it would be perfect if SmartGit would convert all line endings to CRLF on "download" and back to LF on "upload".
Functionality to create a range of patches, all labelled sequentially
In the log view you can select a single commit and use the 'format patch' functionality to create a single patch.
However, I frequently have the need to select a range of sequential commits and make patches for each commit.
Basically the same functionality as for example 'git format-patch -3' to create 3 patches from the top 3 commits. SmartGit does not seem to provide this functionality. Why not?
Syntax Highlighting: support for DataFlex language
Please add DataFlex as a supported language for the Syntax Highlighter.
Kind regards
Marco
Allow doing SmartGit actions when an action is being executed
This is something I wanted for years. Oftentimes when I'm doing an action with SmartGit that takes a few options, I can't do almost anything else in the UI until the command is finished. This means that a big chunk of my time using SmartGit is spent twiddling my thumbs, waiting for SmartGit to finish something so I can do the next thing.
For each of these actions, I have to wait until it's finished before I can do the next. It's annoying. I wish I could do them rapidly one after the other, and SmartGit could execute them asynchronously. If one of my actions results in an error, then stop the queue and let me know, but that's likely to be uncommon.
Allow opening the Log while a push is taking place
When a push is taking place in the main window, or any other action, I can't open the Log. I have to wait for it to finish. I wish I could open the log despite it not being finished.
SmartGit needs to be able to handle multiple user profiles and SSH keys.
This is one of the real hassles with Git that should not be done manually. I would buy this product in a heartbeat if it handled this functionality.
compare two seperate files in same repo
It would be nice to be able to use SmartGit to compare two files in the repo
Customer support service by UserEcho
