Allow me rename file like git mv command. It may be context menu or auto recognition of file changes.

I would love the ability to export my SmartGit settings into a single config file so then I can easily & quickly import my settings later when reinstalling or installing on a new system.

I am aware you can sync/copy settings from one SmartGit installation to another by copying over the various .XML files in the SmartGit settings folder, but this can be messy and cause problems if not done correctly.

To avoid horizontal scrolling

Git lfs is a great, additional feature when using Git for situations, where blobs need to versioned, too. I would love to see a nice GUI integration of Git "large file storage".

Until now, modified EOLs are nearly not visible in SmartGit. There's only a label which shows for example "EOL: Unix vx. Windows", but it's very easy to overlook it because the diff itself shows no changes.

In addition, if a file has different EOLs, SmartGit just says "EOL: Mixed" but does not show which line has which line ending. And staging/discarding them line by line is also not possible.

In my opinion, differences in EOLs should be visible in diff viewers with some kind of symbol on each line, like "git diff" does. So the user can see which line has which line ending, and can even fix them by staging or discarding line by line, just like all other changes.

This feature may be useless on Windows with "core.autocrlf=true", but on other operating systems or with "core.autocrlf=false" this would be extremely helpful because one can see and fix introduced EOL changes.

See also: https://smartgit.userecho.com/topics/655

Tool that I'm currently using allow this and it saves me a lot of scrolling so for me it would be nice feature.

When fetching from a remote, allow the choice to prune (delete) any local branches, which are tracking a remote branch that has been merged.

This is quite a common task, especially if you work in a team that uses a lot of feature branches and Pull Requests. Stackoverflow related question

P.s: This is a feature available in SourceTree.

To better understand your requirements, vote either for:

Topic #1408: Improve usability under Windows Subsystem for Linux with GUI (WSLg)

or

Topic #1409: Improve working with repositories located on the Windows Subsystem for Linux (WSL)

It often happens during a merge that a number of files in a repository will have conflicts. It is already possible to apply the conflict solver to individual files, but I would like to propose the following workflow:

During a merge when multiple files are conflicted:

1. Select all the conflicted files.
2. Choose to activate the Conflict Solver.
3. For each file in the select list open the conflict solver (as is done for a single file)
4. User solves conflicts (or decides to cancel), thus terminating the conflict solver for that file.
5. SmartGit shows a dialogue with the following options "Stage file", "Skip file", "Cancel".
6. "Stage file" will stage the file and SmartGit will automatically open the conflict solver for the next file in the selected list.
7. "Skip file" will not stage the file, or mark it as resolved, etc, but will move automatically to the next file in the list, opening the conflict solver for the next file.
8. "Cancel" will stop the process completely. Files already staged will remain staged.

This will, in my opinion, make merging multiple conflicted files much easier. There could also be a button on the ToolBar which starts the conflict solver for all conflicted files in the current repo, without the user having to select them all.