Our team would very much like the ability to customize the format of a cherrypick commit message, by specifying a format string in the smartgit.properties file. We are imagining a format like:

-Dsmartgit.cherryPick.customCommitMessage="(CP %2 from %4) %3 (Cherry picked from commit %1)"

%1 = full SHA
%2 = short SHA
%3 = original commit message text

%4 = branch original commit was cherrypicked from

That would really help us understand our development flow better when looking at complicated branch hierarchies in the log window, as we could make it immediately clear when a commit is a cherrypick, and where it came from.

It also allows us to add information we need to the commit message to enhance our build and code review automation.

Because opening large repositories is quite slow (~5-10s), I keep all my frequently used repositories open. But unfortunately all these repositories are closed every time I want to open one more repository. Selecting and opening all the already opened repositories again just to keep them open is quite annoying. And also when cloning or adding a new repository, it will be opened automatically while all other repositories are closed.

In my opinion, repositories shouldn't be closed automatically but only when the user triggers it manually.

It would be nice if smartgit handled remote repos as well with mercurial as it
does for git.
In particular it would be nice to be able to see what the difference is between a
local and remote tracking branch before actually puling, as is possible with the
smartgit "log for" view
(even though this is a bit hidden in smartgit, first pull, then fetch only).
TortoiseHg does this better by offering a "check for incoming/outgoing changes"
tool buttons.
Also it would be nice to be able to add/view remote hg repos from inside smartgit.
currently it seems one has to manually edit the local repos .hg/hgrc file.

Git has become extremely widespread and more and more users who are not programming C++, Java or the likes are using it. In this context Git LFS is quite important in many cases. However, its use is still quite geeky and non-intuitive.

It would be great if Smartgit offered a more intuitive, GUI-centered way to use and integrate Git LFS in the normal, daily code versioning (or, in this case, FILE versioning) workflow.

It would be nice to auto-fill the tag name as the branch name in the text box when checking out a tag.

Currently the text box is empty and i have to manually type in the tag name. This seems like a small improvement in terms of implementation and would really help :)

Right now I have to select all repos. Please, add a new right click action

When rebasing, using the rebase button or interactive D&D rebase,

it would be useful to optionally skip commit verification (as per the --no-verify flag, and consistently with the default behavior of git rebase -i).

That is because some commits in the history, for technical reasons, sometimes have to not pass the commit verification. For instance a commit containing a patch file must be allowed to have trailing whitespaces.

Currently this prevents to use the interactive rebase feature, as moving a commit around the non-conforming commit will cause an unsolvable error. Doing the same thing using "git rebase -i" works just fine.

Copy the name of the branch from branch panel.
Copiar el nombre de la rama, desde el panel branch.

I always use the newest version of Mercurial and sadly SmartGit/Hg doesn't support Mercurial 3.8

is there a reason why there has to be a supported version? it should be like git where it doesn't really care what version you have installed

Currently, the compare shows a left and a right pane so only up to the half of the screen width is used. Often to less for seeing the full line without scrolling horizontally.

Suggestion: (optionally) show a 2-line view below both, the left and right panes, that show the left focused line above the right focused line. That way you have a longer display and easier can spot differences.