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]

Hey SmartGit folks,

I've been thinking about a couple of tweaks that could make SmartGit even smoother for everyday tasks. First off, how about a quick shortcut for amending commits? Right now, we have to tick the "Amend" box in the commit dialog, which is fine but a bit slow if you're doing it a lot. A single keypress or a direct button for this would be super handy.

And for those times when we're just fixing up a single file and want to amend it to the last commit, wouldn't it be cool to have an option to do that without the commit dialog popping up? Like, right-click the file and choose to amend commit directly—using the last commit message as a default. It would streamline those quick amendments.

What do you guys think? Could be some neat quality-of-life improvements, right?

Cheers!

For those of us who contribute actively to opensource projects based on forgejo(for of gitlab) platform, i.e. codeberg, it would be nice to have some sort of integration, i.e. referencing issues, query issues, list pull requests, etc.

Currently, when investigating a file (right click file/investigate), the Diff view :

only shows the diff between the selected file (New contents) and the previous version (Old contents).

It would be nice(r) if it was possible to select a previous version in the Navigation pane e.g:

and have that replace the Old contents so one could compare (i.e. not unlike the functionality from using the working tree view and doing it there - just focused more in the Investigate window as then one is looking at the one file rather than the whole commit)

There should be following root categories:

• "Local Branches"
• one root category for each remote
• "Tags"

The explicit root nodes for each remote could also allow Remote-related operations (like in the Log window).

It would be useful to see a name of the branch we're going to force-push.

When opening the file-specific log view and selecting two commits to show the diff, all the files modified between these two commits are shown. Since the intent is to look at the initially selected file, it would be much better if the filename was set by default in the filter, or maybe have an option to only show the logged file which would work across file renames.

When a repo's master branch has incoming changes and the repo is checked out to master, SmartGit displays the helpful down arrow indicator. But, if the repo is checked out to a non-master branch, there is no indicator for the branch-to-master status (as the indicators are for the checked out branch). To learn if a repo's master branch has incoming changes to update and rebase my working branch on, I have to click on each repo to review it. This requires reviewing the graph to find those commits and see how they align - is the branch missing commits from master.

The current product I'm working on has over 20 repos. To help this, perhaps an indicator on a branch in the Branches view when the branch is behind on its master branch?

Hi.

I've noticed that many times while I have selected a branch and want to only fetch or pull that specific branch which is set to tracked to a remote repository, there is no option to do it. The option "Remote->Fetch" seems to fetch all the branches from the selected repository, filling up the local remote references with a lot of not-want-to-download branch references and taking a lot of unnecessary time.

I'm currently working on Log Window, which seems to offer more functionality than Standard Window. So, on the Log Window I can not find a way to fetch/pull only the selected branch from it's tracked remote. This would be similar to the command "git fetch <tracked-remote-name> <selected-branch-name>" or "git pull <tracked-remote-name> <selected-branch-name>".

Thus, if there indeed no way to do this, is it possible to add commands "Remote->Fetch selected" and "Remote->Pull selected" in the Log window (and any window in general)? When clicking on these command it's expected the tracked remote branch of the selected branch to be fetched/pulled, and if the local selected branch is not tracked then to propose to set a remote track first. If the selected local branch is tracked but has been deleted from the tracked remote repository to just inform the user that the tracked remote branch doesn't exist anymore.

Thanks