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.

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..

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.

WSLg can be used to run SmartGit in Linux environment while using Windows as main development OS.

We have tried it briefly and SmartGit seems to mostly work file in WSLg.

Out findings are summarized here:

https://docs.syntevo.com/SmartGit/HowTos/Running-on-WSLg.html

There are a few nuisances, such as SmartGit updates failing, which can be improved.

The current plan is to spend a couple days in the next couple months to try to fix nuisances.

However, if this proves to be complicated, we'll get back to more popular feature requests, unless this topic gains more votes.

If you're interested in using WSLg with SmartGit, please describe your use cases and any problems you encountered.

Note: this topic is about running SmartGit from within WSLg. If you want to access repositories on WSL from Windows, vote for topic 1409.

Upon switching branches in a repository that contains submodules where the other branch does not contain this submodule anymore, the folder in the repository shows the state "Nested Root" . 

This gets really annoying since one has to manually navigate to that folder and delete it.

In this use case it would be helpful and to others less confusing to add the following:

* A dialog which asks what to do with that folder

  * Display an explanation of what happened. This is not an obvious and easy case for people.

  * The recommendation would offer deletion of this folder if it does not contain uncommitted and unpushed changes in that submodule (that can be determined opening a git shell in the folder and see what `git status` returns.  

  * If it does contain uncommitted commits that haven't been pushed, either abort changing branches or display this information to the user.

In the Git-Flow 'Finish Feature' dialog is should be possible to select ‘Create Pull Request..’ as well.