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.

Occasionally, I need to review the code around a particular commit.
However, I can't seem to find a way to directly navigate to a particular commit without applying any filters.

I found it on gitkraken

but on smartgit

It would be nice if the branch structure in the Standard Windows view could be set like in the Log Windows view where SmartGit shows local branches and remote branches in a tree view. Also branches are grouped by paths:

I think the UI would be more consistent if the layout of "Local Files" and "History" tabs would be similar in the Standard Window:

History in the center of the window and commit messages and changed files to right.

Please allow individual coloring of the entries in the branch window (accessible via CTRL+SHIFT+2). It should be possible to define both the text color and the background color separately for each branch as well as depending on the status "checked out" and "not checked out".

For this purpose, it would be an option to define classes in the settings, e.g. "warn" or "deploy", and then specify "warn" with regular status has red text color, "warn" with status "checked out" has white text color with red background. One can then assign a class to individual branches in the branch list.

This way, branches where a push results in subsequent actions (e.g. deploy to production) can be clearly highlighted ( and their potential impact...).