In the branches tab, sort all grouped branches to the top of the list.

After every group is listed, then show all "singles" branches which aren't grouped under a root.

If that's not clear, I'm basically asking you to sort the list the way Windows Explorer handles folders/files.

Folders are listed first, and then below that you see the files.

Please, add the in-place copy and in-place rename features as implemented by e.g. Total Commander and Midnight Commander - the functionality is assigned to Shift+F5 and Shift+F6 shortcuts.

I'm aware that files can be copied and renamed in-place using F5 or F6 keys - but hey, the usage is not that fluent.

And, please, don't invent your own shortcuts if there is a long-term tradition of their assignment. Shift+F5 stays for Create Link in SmartSynchronize - and this is not good, because people may use other commanders (possibly on other systems) at the same time and the muscle memory works (in this case, it works against SmartSynchronize, as it is a new kid on the block). Moreover, the users of "commanders" are quite conservative, I believe - if they were not, they'd be using the more "modern" file managers, e.g. Windows Explorer, Dolphin, Nautilus, etc.

1. Log window: Select two commits (click, then ctrl+click).

2. The Changes button in the toolbar (F4) is disabled. (Why? Am I prohibited to make a diff at this moment? This is illogical.)

3. Click anywhere inside of one of the diff widgets. Now the Changes button becomes active. (It should have been active in step 2.)

Note: The button tooltip reads: "Show local changes. F4" I think the word local is superfluous here. We can't show remote changes anyway, any remote data are first downloaded to the local computer by git. Does it mean "Show changes to the working directory?" No, it can be used to show a diff between any two commits. I think "Show changes. F4" or "Show a diff. F4" should be enough.

I would love to see the new "Working Tree" and "Index" items (optionally?) combined into one item in the Log Graph view (e.g. as "Working Tree, Index"), where Files and Changes would work exactly like the old Working Tree Window, so I never have to switch between the Working Tree and Index items in the Log Graph while examining and manipulating modified and/or staged files.

For me, as a programmer, a "change" means a modification of a few related lines in code.

That is, if I have two files, aaa.py and bbb.py and I modify lines 10, 15, and 20 in aaa.py and lines 100, 200, and 300 in bbb.py, this means I made 6 changes in 2 files. (I believe this implies that the command git add --patch would be used 6 times in total.)

However, the "virtual nodes" in the Commits section of the Log window says 2 changes, which suggests that only two changes have been made. This is quite confusing. Please, change its wording either to 2 changed files or 2 files changed (don't know which one is better, I'm not a native speaker).

Thank you,

Peter

Nearly every developer is in a situation where they have api tokens, secrets, or other specific local configuration that they change on their box but don't want to commit them or push them.

It would be pretty amazing if SmartGit supported a feature where you could set specific line modifications in a file to be ignored and/or excluded during a commit. 

Currently when a commit doesn't exist within a submodule, but a parent project is trying to point to it, "Could not determine submodule commit" is displayed. I would like the SHA ID also added to this message.

This will be useful for writing the ID on a lump of wood and repeatedly hitting a co-worker with.

Or most likely tracking down where and why this has appeared in the first place.

Using the Conflict solver I can browse to the base changes, but I don't see the commits affecting the changes in both trees. That would be a great benefit for solving conflicts.

Thus, adding the git blame window to the line with the change would be good, either as a single line below each file or as the standard blame window.

I am working on a big project and therefore, sometimes I have a lot of branches (sometimes their name is close to another) that are in repo and under review. Therefore, unless I checkout to a branch and look at the logs, I don't remember what this branch does/fix/improve.

The Message box helps to attach Jira link (or more information) to the branch. Therefore, I don't need to checkout anymore to get more info about the branch.

I would really like to be able to see the Semantic Version of the repo. I think that this could be set so that if there is a GitVersion.yml Config in the root of the repo then SmartGit could use it show the semantic version number of the branch.

https://gitversion.readthedocs.io/en/latest/