For a long time SmartGit has a combined view showing working tree and index files in one table. There, staged files are kept selected after the state change.

If I understand this correctly, this would just commit the last staged (and still selected) file, right?

22.1 preview 1 will have it except of "Either do not pre-populate the list of found repos, or indicate which paths have been searched to produce it."

What should happen if you have staged some files, select other files and stage them (keeping them selected). Now you invoke Commit. What should be the choice - only the selected files or the staged files? I would think, that 99% of the users would expect the staged files to be selected.

Yes, we need to white-list the Windows 11 version, because we had to use inofficial API.

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?