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 precise as possible, so we (Syntevo) and other users will understand what you want. A plain request "SmartGit should look cool" is too vague because we don't know what we should change, and hence will not be approved by us.


Thank you for your help!

0

Export/Import settings and/or better `git push/clone` my SmartGit settings to my repo.

kyb 1 year ago 0

It would be very nice to save SmartGit settings as Git/Hg repo. And simple buttons Export and Import in Settings dialog is very useful when working on several machines or OSes

0
Declined

Make "Output" window an editable terminal

Alireza 1 year ago • updated by Thomas Singer 1 year ago 2
0
Declined

Use Qt for the GUI to improve rendering and accessibility

dfgbefrgb 1 year ago • updated by Seb D 1 year ago 1
0
Completed

Support signing git commits

Marcus Ilgner 1 year ago • updated by Thomas Singer 1 year ago 3

When creating a commit, add a checkbox that enables signing commits with GPG, just like using `git commit -S`.

0
Completed

Spell Check in Commit Message Window

Leigh 1 year ago • updated by Thomas Singer 1 year ago 2

Spell checking in the commit message window would be very helpful for those late night bleary-eyed commits.

0
Completed

Push: add support for "git push refs/for/master"

Adrien Béraud 1 year ago • updated by Géza Husi 2 months ago 5

We use Gerrit for code review, and integration with smartgit could be better.


Gerrit wants commits ready for review to be pushed to special branches like refs/for/master etc.

SmartGit has no sort of special support for those branches or other Gerrit features, so it's currently more convenient to use the "git-review" command instead of the GUI.

0

Separate command output log file (in addition to log.txt)

Craig Caulfield 1 year ago • updated by Marc Strapetz 1 year ago 5

The output log is great idea. I can see (and learn from) the commands being executed.


You can go through the log files in the .settings directory but they're logging lots of other activity besides the straight Git/Mercurial commands. It would be handy to see just the VCS commands and their output.

0

tutorials about using smart git and explaining repositories

shany 1 year ago 0

i wish i could understand more about different concepts of github instead of continuously calling my boss!

0

Log: Copy Relative Path when multiple files selected

tokodilajos 1 year ago 0

In the Log window when you select multiple files in the files tab, you can't use Copy Relative Path. You can use it only when one file selected.

0

When commit, update headers

Pillo 1 year ago 0

when commit add (if is the first commit of file) or update a header on files with user details (who create the files, who update the files, the time and date, etc) sorry for my bad english