Hi

Recently I had to move in a different disk location a folder with some repositories, which I had already setup in the "Local repositories" window. Then I faced the problem that in the "Local repositories" window I had no option to update the repositories paths with their new disk location paths. The only way was to erase them one-by-one and add them on-by-one in their previous groups, facing in each addition the need to close the repository which automatically was opening too. It was a bit annoying and prone to errors.

Thus the feature I'd like to see in SmartGit is to be able to right-click on the wanted repository in the "Local repositories" window and have an option to edit the disk location of the selected repository.

Such a change should actually automatically do what someone can do manually till now:

1. Keep the selected repository's parent group from "Local repositories" and the repo name (if repo is renamed)

2. Delete the repository from "Local repositories"

3. Add at the kept parent group of "Local repositories" the repository at the new given path. Rename as the previous name.

4. Do not open the updated repository (because user may want to change paths of other repositories too)

I think this would be a very handy feature for those who at some point may need to move folder(/s) with repos elsewhere in their local machine...

Offer a shell to execute (Git) commands. Allow to easily select file paths, e.g. by dragging the file to the shell control.

"committed diff" is activated when a single commit or a range is selected.

in this state the context menu on changed hunks in diff window only shows "Copy"

It would be nice to be able to stage the reverse of the selected hunk.

Thanks.

Currently, we can drag-and-drop a repository folder directly under any group in SmartGit, but if the repository doesn't exist, it just says "The dropped repository is no Git repository". So we have to do Repository > Add or Create... each time.

Instead, if the folder has no repository yet, the app could offer the user to initialize one, then add the repository to the group it was dragged to on the go.

Suppose I want to play with certain branch in the repo of which I already have a worktree on another  branch.

I try Repository->Add worktree  - oops, it tells me that I don't have that as a local branch...

Can this Just Work, please? All I want is get me a new working directory for certan branch, presto.

If this takes some actions under the hood, please do this for me.

* I cannot do check out on this branch, because this will stomp on my current working directory (where files are already open in my IDE ...)

* I don't want to go all the way from Repository->Clone.... enter the repo URL, then the branch....

Diff tool editor is a very handy tool for me to perform modifications on the spot, without a miss out anything.

However, I may sometimes switch between IDE and SmartGit's Diff tool editor.

When I perform an edit in IDE and forget to refresh the currently opened Diff tool editor, it will override all my IDE changes, if I press save in the Diff tool editor.

It will be great if the Diff tool comes with a file monitoring feature with the current logic

1. If it detects the file on disk has changed, and there is no change made in the Diff tool editor itself, it will silently reload the file.

2. If it detects the file on disk has changed, and there is a change made in the Diff tool editor, it will show a prompt, to ask the user whether he wants to reload.

Thank you.

I have 1000 + branches. 

please re-use the branch grouping feature for the standard window. So I can see my branches in the 5 main categories again.

In Windows 22H2 (latest) white scrollbars and menus are back. On the previous windows 22H1 version everything was fine

SmartGit 22.1

For those commits which are displayed (the graph roots are defined by your local branches), optionally also show tags, as the Log window does.

Currently, files in the Local Files and History views are shown as list. The user only has the option whether to show it as name (path) or path/name. Depending on the directory structure the path part can get quite wide which might cause issues in the History view:

Alternatively, there could be an option to show the files as tree-like list adding directory entries for each parent directory (without a way to collapse directories):

This might require less horizontal space (but a lot more vertical space).