SmartGit allows you to create and apply a patches for Git, but not for Mercurial. Atlassian's SourceTree and the tool within Intellij IDEA have a context menu against log entries to create a patch from single or multiple commits.

Tools configured in the Preferences should work on the Log's File view in a similar way as in the main window

https://plugins.jetbrains.com/plugin/7566?pr=idea

I would love to have the ability to "zoom in on" or temporarily maximize the changes view panel. This is a feature on VS Code side and bottom panels, and I find it really helpful to be able to toggle that quickly.

Currently, filename autocompletion in Commit message edit field works this way: when you press Ctrl+Space, a popup will show matching filenames for:

- if there are no staged files, all unstaged files (so all files with a modification, basically, although filters may affect this)

- if there is at least 1 staged file, all staged files

However, this is not compatible with my workflow, where I write a bullet point in my commit message for each file or group of files to explain their changes, *before* staging them. So on the contrary, I need autocompletion for unstaged files. Sometimes I also want to refer to a file even if it has already been staged, so ultimately I'd need autocompletion for all files.

To cater for all needs, SmartGit could provide flexible Commit message editing options (either in Preferences or in the small hamburger menu at the top-right of the commit message area, or both), to enable filename autocompletion for:

- all files

- unstaged files only

- staged files only

- disable autocompletion

(2 checkboxes for the 2 categories would be enough to produce the 4 combinations)

In addition, for people who like the current fallback system, an extra checkbox:

- if selected group (staged or unstaged) has no files, fall back to the other one (unstaged or staged, resp.)

This final option only makes sense if you chose staged files only or unstaged files only, so grey it out otherwise, I suppose.

I would like to have a commandline option available for smartgit.exe which enables me to move a repository into a 'Group' in the Repositories window. 
At the moment this is a manual activity which is taking too much time since, in our situation, the number of involved repositories is increasing  rapidly over 30.

When this commandline option is available we can use scripting to move these repositories to the correct group which saves lots of time and reduces errors.

Do you have support for Jujutsu on your roadmap? We have developers using Jujutsu and I'm also tempted to use it because it has some really nice features. Stacked PRs and the option to resolve merge conflicts later would be the two features I'm most interested in.

BR

Martin

Currently, the repositories can be grouped under custom groups, much like placing files into separate folders.

I would like to propose that you implement the same feature for local branches. Another variant could be to allow the tagging of branches. I don't mean the git tagging, I mean assigning custom labels to a branch and the providing a quick way to filter the branches by one or more selected tags. Either way works for me, but probably I would prefer the folder approach.

The reason for this is that I have lots of local branches that correspond to issues I've been working on throughout time. It becomes harder to figure out where some branches are at, especially when I have to switch context. I would like to
create a group called "Done" or "Implemented" and move the branches to this group after they are done to get rid of the visual clutter.

There were some previous suggestions on these lines under Branches view, though they are not exactly the same as my request.