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 :)

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.

We have standardized on branch names on the format <username>-<ticket-id>-<description>. Allowing '-' (or any other character) as the grouping character would make grouping more flexible. It also happens that the same ticket has more than one branch, so multi-level grouping would be nice. Sort of like an expanding directory structure..

problem:

* its very hard to search who made prev. changes (eg. in months)

solution:

* so ideal is to have tool, which can track history of one line in file to context

* you will just selected lines, which u're interested in

* and this feature will show history only of this selected lines of code

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.

Hello,

Could an option be added to include the --update-refs arguement for rebase operations? Either in drop down menu during rebase or just a checkbox in preferences / advanced settings would be fine from my perspective.

I quite often work on large features that then get split into multiple branches stacked on top of each other.

I generally work on projects using a rebase strategy rather than merging branches into main, so I end up wanting to rebase the stacked branches onto the head of main for testing / submission.

Currently I end up needing to drag/drop the whole branch onto main to rebase it as just the lastest branch name, then manually drag the intermediate branch labels up to where they're supposed to be in the stack which is quite tedious and error prone. 

Alternatively I drop to the terminal to run the rebase there with --update-refs and it moves all the intermediate branches for me along with the rebase.