Thanks for the details.

> Either do not pre-populate the list of found repos, or indicate which paths have been searched to produce it.

The same directories are automatically searched as with during the setup wizard. This means, it scans the home directory and on Windows all local hard drives.Not searched are $Recycle.Bin and the locations where the env vars ALLUSERSPROFILE, ProgramData, ProgramFiles, ProgramFiles(x86), SystemRoot, TEMP, TMP, windir point to.

> Provide a way to specify which group the repos will be added to.

For 22.1 preview there should be improvements to add the repositories to the same locations as Repository | Add or Create does - in the best matching group.

When exactly the pre-commit hook should be invoked? On every refresh?

It is not our intention to simply copy the command line features in SmartGit, but rather find solutions that better suite a GUI application, especially for those users who have not used the command line Git.

Is it necessary for you to have it in the interactive rebase or would it be sufficient to select the commits and then choose Modify or Split Commits from the context menu?

I'm not convinced whether it is the best thing to pollute each command that somehow commits with such a low-level option. Maybe we should add it to the repository settings?

In the SmartGit settings directory is a gravatar-cache directory. There you can store "<email-address> <size>.jpg" files (size=32, 64, 128).

Please note, that Pull might be a destructive operation - it can product conflicts, especially if there are local changes. I would prefer to avoid getting reports about: "SmartGit screwed up my files when I clicked into the SmartGit window."

Note, that the toolbar commands perform exactly the same as the corresponding main menu item.

Please send a tiny test repository and exact steps to reproduce to smartgit@syntevo.com. Thanks in advance.