When I start typing and selection start jumping in the branches tree I would go one step further and actually filter the branches tree.. that way I can be better guided into finding what I'm looking for. 

Who ever worked with Jetbrains Rider or other IDE they know what I mean. Virtually EVERY list () can be quick-filtered on the spot which is very powerful. 

We use nested groups to great effect in the Repositories view to manage our all our projects, often consisting of 100+ repos each. To arrange the repos in these groups we can either drag and drop into the group or use the context menu and choose "Move To".

With a hundred repos in a group dragging repos to another group does not work (in the past it would scroll slowly if you moved to the top/bottom of the view but this no longer appears to work) so we now use the context menu. The issue with the context menu is that it is a flat representation of all the groups. There are up/down arrows at the top of the context sub-menu but these only adjust the menu one line at a time which is also very slow.

My feature request is to make the "Move to" menu follow the same hierarchy as the groups in the Repositories view, using sub-menus rather than just spaces. This could be an optional feature enabled in config to not break other customers' workflows.

Some stats about my setup:

Number of repos managed by SmartGit: ~2800

Number of groups defined: ~210 (42 level 1, 146 level 2, 22 level 3)

SmartGit Details

Version: 23.1.3 #20195

Java version: 17.0.5+8-LTS (c:\program files\smartgit\jre)

Windows version: Microsoft Windows [Version 10.0.19045.4412]

We copy full Commit / File name (with details) by Ctrl+C, and short Commit name by Ctrl+Shift+C.

Please realize copying short file name (i.e. filename only) by Ctrl+Shift+C.

Please support working with Git-providers based on https://gogs.io/

Currently, the "Branches" pane shows a count of the number of branches in each top-level group (e.g. "Local Branches (3)" or "origin (27)"). And when "Group tags and branches by path-like name" is selected, there's a sub-group for each initial path component, with all branches having the same path component underneath that group.

Problem: we use path grouping for different developers, and some developers have gotten out of control on how many of their branches are still hanging around. But, it's hard to see which developer has lots of branches and which has few.

Suggestion: have the sub-groups display the count of branches within that sub-group.

Hi

while the font size of the SG application is configurable with the defaultSize ui low level props, the font size of the Merge request comments is apparently fixed and very small (the comments are almost unreadable). Is there a way to increase this font? If not, it should be possible to do it, please!

Thanks in advance

It would be great to run external tools on other contexts than the whole repo and files.

E.g., I like to manually prune remote branches. But for a repository with more than one remote, I cannot do this without using the command line because I cannot select the correct remote context to run my command.

Similarly, it would be great to also have tools available on branches and tags.

The easiest way for the user would be to add a "Tools" sub-menu entry on the context menu of the branches view items (and maybe the captions in the log graph).

This caption should similarly to the confirmation dialogue parse the replacements, so that the user can get a good description of what will happen.

For example:

label: "Prune remote branches of ${remoteName}"

command: ${git} fetch --prune ${remoteUrl}

Can we have fast-forward merge feature for branch in Standard workflow?

Hi,

I'm using a non-commercial license to access public repos. Every time I had to click to "verify this repo" - it is very annoying and unnecessary. If I'm using a non-commercial license, it's expected that I will keep only public repos inside SmarGit since I cannot open private ones anyway.

Please don't make the life of non-commercial users more difficult.

When you LKM on a file and click 'Log' - it shows filtered history with only commits that changed that file, but it doesn't show stashed changes. The 'Branches' menu in 'Log for <file>' window doesn't have 'Stashes' folder, while 'Log'  window does have it.