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!


Commit IDs (SHAs) in commit messages should be hyperlinks with opens to view that commit

Christopher Kline 3 years ago updated by Thomas Singer 2 years ago 1

Often our commit messages refer to other commits, like:

"This commit fixes an issue introduced in commit 1d441145, which ..."


"59c5792d50c49f77ca9f044fa03c108c5f515de8 introduced a bug which caused ..."

Currently I have to manually copy the commit ID, then (opening a new log window first if desired) paste it into the log window search box.

What I'd like is a way for those commit IDs to be automatically highlighted, and when you right-click on them you get the option to reveal the commit in the current log or reveal it in a new log window.

To my knowledge, there doesn't seem to be a way to do this via the Bugtraq integration.


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

Marc Strapetz 3 years ago updated by Patrick Lehmann 3 months ago 3

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

[submodule "meta"]

path= meta

url= ../meta



All SmartGit settings in a single dialog

Thomas Hansen 3 years ago updated by Christopher Kline 3 years 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).


Gerrit as hosting provider

leuschns 2 years ago updated by admin1 2 years ago 2

- add Gerrit as hosting provider

- config needed: server name, server port, optional path to ssh key empty uses default, like clone command that just picks up default file)

- connect to gerrit via ssh (command line would be 'ssh gerrit ls-projects') it responds with plain text, one repository name at a time

- clone URL becomes ssh://SERVER:PORT/REPONAME.git (append .git)

hosting provider

Repositories view: group in group

Mickaël PERRIN 3 years ago updated by Dan Gibson 7 months ago 18

Groups are a good way to organize git repos, but what about organizing groups in groups ? It would add a useful tree view for organizing projects...


Ignore File: ability to specify which .gitignore file to use

Chris Jaquet 3 years ago updated by Thomas Singer 2 years ago 8

Having .gitignore files throughout a project's folders can make it difficult to manage the ignore rules for a particular project. It would be helpful when ignoring a file to be shown a dialogue which asks the user which .gitignore file to use - current folder (i.e. the folder containing the files to ignore) or repository root (the .gitignore in the root of the repository). An additional "nice to have" would be to be able to specify the default using a checkbox on the dialogue (as is done with the "Reset" dialogue in the log view.


Support for git-subrepo

alexfouche 3 years ago updated by Andreas Völkel 3 years ago 1

Can SmartGit support git-subrepo ?

It permits to "embed" git repositories within one as normal files (and not like submodules), so it permits to clone the complete repository like normal and without even needing needing to know about it, branch at will without issues, and yet permits to push and pull changes to these subdirectories from their upstream git repositories. It also does not have the drawbacks of git-subtree.

This command is an improvement from git-submodule and git-subtree; two other git commands with similar goals, but various problems.

It assumes there are 3 main roles of people interacting with a repo, and attempts to serve them all well:

  • owner - The person who authors/owns/maintains a repo.
  • users - People who are just using/installing the repo.
  • collaborators - People who commit code to the repo and subrepos.

The git-subrepo command benefits these roles in the following ways:

  • Simple and intuitive commandline usage.
  • Users get your repo and all your subrepos just by cloning your repo.
  • Users do not need to install git-subrepo, ever.
  • Collaborators do not need to install unless they want to push/pull.
  • Collaborators know when a subdir is a subrepo (it has a .gitrepo file).
  • Well named branches and remotes are generated for manual operations.
  • Owners do not deal with the complications of keeping submodules in sync.
  • Subrepo repositories can contain subrepos themselves.
  • Branching with subrepos JustWorks™.
  • Different branches can have different subrepos in different states, etc.
  • Moving/renaming/deleting a subrepo subdir JustWorks™.
  • You can init an existing subdirectory into a subrepo.
  • Your git history is kept squeaky clean.
  • Upstream history (clone/pull) is condensed into a single commit.
  • You can see the subrepo history with git log subrepo/<subdir>/fetch.
  • Commits pushed back upstream are not condensed.
  • Trivial to try any subrepo operations and then reset back.
  • No configuration required.
  • Does not introduce history that messes up other git commands.
  • Fixes known rebase failures with git-subtree.


Upgrade should be entirely seamless

Ram Rachum 3 years ago updated by Walt Destler 3 years 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.


Branches view: allow more than one path hierarchy for grouping of path-like branch names

mhoss 3 years ago updated by Florian Kaufmann (Borm) 1 month ago 3

Allow more than one path hierarchy for grouping of path-like branch names

e.g. issue/internal/DEV-XYZ


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

Colin Richardson 3 years ago updated by Christopher Kline 3 years 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.