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!

+19

Upgrade should be entirely seamless

Ram Rachum 1 year ago • updated by Walt Destler 11 months ago 2

I'm tired of opening SmartGit and waiting for it to upgrade itself, or even see the toaster message notifying me of a new build. Just do the upgrade completely seamlessly, like Chrome, without me even knowing SmartGit gets upgraded.

+19
Completed

Conflict Solver: show base file [SG-7715]

Marc Strapetz 1 year ago • updated by Seb D 6 days ago 26

In addition to the left - merge - right view, have a left - base - right view which shows the "base" file (as it's part of Git's index). This helps to understand the actual independent changes in the left and the right fork.

Git
+18

All SmartGit settings in a single dialog

Thomas Hansen 1 year ago • updated by Christopher Kline 11 months ago 6

Currently there is:

- repository / settings

- edit / customize

- edit / settings

- remote / properties

- changes / settings


How about making 1 settings dialog under "edit/settings" and putting all setting in there. In tabs or ordered in a way similar to how Visual studio does it (tree view).

+17

Add subtle indicator that commit message is multi-paragraph

Sync 9 months ago • updated by a.doerfler 2 months ago 7

In both the Journal and Log view, we don't know if there are more information in the commit message unless we click it and look at the [Details], because SmartGit only displays the first paragraph of the commit message in the [Commits] column (a normal Git convention, adhered by most Git GUIs). It would be nice if I am able to know which commits have extra info, and which commits don't.


Currently, commit messages that don't fit the column are truncated with an ellipsis. One idea is to move this ellipsis limit a bit further to the left, and add a tiny light-gray arrow-down icon (or anything better) to indicate that there are more paragraphs for this commit.

+17

Highlight Parent commit(s) in Log view if parent is not directly below

Colin Richardson 11 months ago • updated by Christopher Kline 11 months ago 1

When commit is selected if the parent commit is not the commit directly below, could it be indicated some how? Dot outline a different colour? Dot fill a different colour? Track Line Colour? I don't mind which. If the commit has multiple parents, then maybe highlight all parents, even if one of the parents is directly below, since that could cause confusion. (I say all parents, rather than both parents, since I have a few octopus merges). It's hard to track all of the lines some times. I know there is Alt+Down to jump to parent, but I sometimes don't want to jump to the commit, I just want to visualise them.

+17
Completed

Log: Files list, please add "Open" and "Reveal in Explorer" in Context Menu

penski 1 year ago • updated by Thomas Singer 11 months ago 14

List of files in main window has context menu with functions like: "Open" and

"Reveal in Explorer"


I miss them in the context menu of List of files of the LOG window

+17

Submodule Add: option at which branch the submodule should be added

Marc Strapetz 1 year ago 0

This should populate the submodule.<name>.branch parameter:


[submodule "meta"]

path= meta

url= ../meta

branch=beta

+17

Images diffs

Petah Piper 1 year ago • updated by Joshua Gleitze 1 year ago 3
+17

Advanced multi-worktree support

Marc Strapetz 1 year ago • updated by Richard Dols 3 weeks ago 8
Git Need More User Input
+16

Configure background fetch interval *per repository*

Sync 11 months ago • updated by Thomas Singer 2 months ago 3

Seems like there is already a parameter to define the background fetch interface.

  1. Please add a GUI for it.
  2. Allow different intervals to be for each repo

Some repos have more activity than others, so I would like to fetch more often for certain repos, and less often for others.