I set "git config core.ignorecase false" in my repositories and I am trying to first stage their new names:

When I select all new names and hit Stage, Smargit issues a command adding both the new and old file names.

The result of the command can be seem next. I am renaming files (in submodules) fixing their case name, for example, from README.MD to README.md, and similar case name fixies.

Adding New names: (Smartgit console)
Alignment> git.exe add --force -- README.md readme.md
AmxxChannel> git.exe add --force -- README.MD README.md
AmxxEditor> git.exe add --force -- README.MD README.md
ApplySyntax> git.exe add --force -- README.md readme.md
BracketHighlighter> git.exe add --force -- README.md readme.md
BufferScroll> git.exe add --force -- README.md readme.md
C++ Completions> git.exe add --force -- README.md readme.md
CaseConversion> git.exe add --force -- README.md readme.md
ChannelRepositoryTools> git.exe add --force -- README.md readme.md
ClearCursorsCarets> git.exe add --force -- README.MD README.md
ClipboardScopeCopy> git.exe add --force -- README.MD README.md
DefaultSyntax> git.exe add --force -- README.MD README.md
ExportHtml> git.exe add --force -- README.md readme.md
FixProjectSwitchRestartBug> git.exe add --force -- README.MD README.md
FixSelectionAfterIndent> git.exe add --force -- README.MD README.md
ForceRewriteSublimeSettings> git.exe add --force -- README.MD README.md
GotoLastEditEnhanced> git.exe add --force -- README.md readme.md
HexViewer> git.exe add --force -- README.md readme.md
IndentSize> git.exe add --force -- README.md readme.md
KeepPastedTextSelected> git.exe add --force -- README.MD README.md
Language - English and Portuguese> git.exe add --force -- README.MD README.md
Octave> git.exe add --force -- README.MD README.md
OpenAutoCompletion> git.exe add --force -- README.MD README.md
OverrideCommitCompletion> git.exe add --force -- README.MD README.md
PackagesManager> git.exe add --force -- README.md readme.md
RememberCommandPaletteInput> git.exe add --force -- README.MD README.md
RichPlainText> git.exe add --force -- README.MD README.md
ScopeHunter> git.exe add --force -- README.md readme.md
SelectAllSpellingErrors> git.exe add --force -- README.MD README.md
SideBarEnhancements> git.exe add --force -- README.md readme.md
SkipCloseForClonedViews> git.exe add --force -- README.MD README.md
SQLKeywordUppercase> git.exe add --force -- README.MD README.md
StudioChannel> git.exe add --force -- README.MD README.md
SyncViewScroll> git.exe add --force -- README.md ReadMe.md
TerminalShortcuts> git.exe add --force -- README.md readme.md
VBScript> git.exe add --force -- README.md readme.md
ViewSettingsFreely> git.exe add --force -- README.MD README.md
WordCount> git.exe add --force -- README.md readme.md

As you can see, the above command is adding both new and old names of the files.

However, after running the above, the working tree lost the renamed status of the files and only the new names were staged as new files, instead of renamed files.

The old file names are still marked as untracked/Missing.

Then, if I try to stage the old names with Smartgit, nothing happens:

Old names: (Smartgit console)
Alignment> git.exe add --force -- readme.md
AmxxChannel> git.exe add --force -- README.MD
AmxxEditor> git.exe add --force -- README.MD
ApplySyntax> git.exe add --force -- readme.md
BracketHighlighter> git.exe add --force -- readme.md
BufferScroll> git.exe add --force -- readme.md
C++ Completions> git.exe add --force -- readme.md
CaseConversion> git.exe add --force -- readme.md
ChannelRepositoryTools> git.exe add --force -- readme.md
ClearCursorsCarets> git.exe add --force -- README.MD
ClipboardScopeCopy> git.exe add --force -- README.MD
DefaultSyntax> git.exe add --force -- README.MD
ExportHtml> git.exe add --force -- readme.md
FixProjectSwitchRestartBug> git.exe add --force -- README.MD
FixSelectionAfterIndent> git.exe add --force -- README.MD
ForceRewriteSublimeSettings> git.exe add --force -- README.MD
GotoLastEditEnhanced> git.exe add --force -- readme.md
HexViewer> git.exe add --force -- readme.md
IndentSize> git.exe add --force -- readme.md
KeepPastedTextSelected> git.exe add --force -- README.MD
Language - English and Portuguese> git.exe add --force -- README.MD
Octave> git.exe add --force -- README.MD
OpenAutoCompletion> git.exe add --force -- README.MD
OverrideCommitCompletion> git.exe add --force -- README.MD
PackagesManager> git.exe add --force -- readme.md
RememberCommandPaletteInput> git.exe add --force -- README.MD
RichPlainText> git.exe add --force -- README.MD
ScopeHunter> git.exe add --force -- readme.md
SelectAllSpellingErrors> git.exe add --force -- README.MD
SideBarEnhancements> git.exe add --force -- readme.md
SkipCloseForClonedViews> git.exe add --force -- README.MD
SQLKeywordUppercase> git.exe add --force -- README.MD
StudioChannel> git.exe add --force -- README.MD
SyncViewScroll> git.exe add --force -- ReadMe.md
TerminalShortcuts> git.exe add --force -- readme.md
VBScript> git.exe add --force -- readme.md
ViewSettingsFreely> git.exe add --force -- README.MD
WordCount> git.exe add --force -- readme.md

Smartgit runs the command, but the files are not staged either as Removed or Renamed files.

The old file names are just kept hanging there on the working tree as nothing happened:

And If commit this, the files are marked as new files add instead of renamed files.

When I have a repository with countless submodules and Smartgit is doing a background refresh, it always keeps resetting my vertical scroll. 

Here:

1. I am scrolling with my mouse up to the top, but Smartgit keeps scrolling back down.

2. And when I am scrolling down to the bottom, Smartgit keeps scrolling back to the top.

As a user of SmartGit I'd like my git client to have the possibility to have its certain (and any) windows on different monitors in any layout I decide to have, which gives more space for that particular window instead of squashing every window on just one monitor. Just take a look how people who create GitAtomic do it. It simply works phenomenal there and I actually think about switching to their soft if that functionality I'm mentioning here won't be implemented soon in SmartGit.

As mentioned in Log: Rebase by drag and drop between Branches and Commits panels, drag-n-dropping commit(s) onto far branches in Smartgit is very hard.

One of the solutions is to let copy source commit(s) by Ctrl+C and then drop them onto the target commit by Ctrl+V.

Add a column next to the commit message in the commit graph which displays the list of changes files. 

by default or opt-in

It is taken my precious vertical space. The behavior old of showing the Abort button on the toolbar was very awesome!

Prtety simple, saving more than 10 search patterns in the log view seems to clear the older ones, I'd like to be able to save more!

https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html

Sample file: https://github.com/flathub/com.syntevo.SmartGit/blob/master/com.syntevo.SmartGit.appdata.xml

The dark theme is nice, but all scrollbars are still light, and so is the window title bar. The scrollbars especially are very eye-catching and distracting. Naturally the lightest and most high-contrast elements stand out most - it's like the scrollbars were the most important thing and in comparison everything else recedes to the background.

For examples of what I think it should look like, try Visual Studio or JetBrains Rider in dark mode.

(On Windows, and yes, I have set Windows to dark mode.)

It would be great if SmartGit would show lines >1st from the commit message with different colors when a user is browsing the log.

We use the 1st line as the issue description and then following lines contain additional information.

Would it be possible to implement such coloring so that additional lines would be shows e.g. with gray color?

Thanks for considering.