I recently found began using the Journal window - however, when working in a branch, it's not useful that it displays "Develop" as the auxiliary branch, so i set it to "None" which showed the branch im working on.

However !... when i create new branches, the default view gets reset to Develop and i again need to clear it to None.

Would it be possible to set the default view of this window ??

as a setting somewhere ..

Detect when the filesystem (Windows) can't sense the filename case differences of a given repo (Linux Kernel) to avoid falsely indicating Example.h is a changed version of exAMple.h. This would avoid indicating that you have uncommitted changes the instant you clone a given repo with only case differences in certain different file names.

For interactive rebase git generates files containing comments starting from "#". But this character isn't hardcoded, it can be changed in git configuration f any other character: ";", "$" and so on. If core.commentchar is not "#", SmartGit can't parse generated file and interactive rebase fails.

The readability would be better if the straight lines are preferred to the curves.

ex.:

hello | operator fails to execute here

diff ${commit}^..${commit} -- "${fileOpen}" | ${git} apply --3way

when i execute same command from mingw64 it works correctly

https://www.tutorialspoint.com/unix/unix-io-redirections.htm

In the log window, I tend to select only have a few branches selected (related to current work) to avoid cluttering log history.

I would like to have this dynamically done via a filter.

For instance, I create branch "ft-issue123", then sub-branches off it like "ft-issue123-fileFixes", "ft-issue123-dbIntegration" etc.

I would then like be able to auto-select branches matching e.g. "issue123", so I automatically get log updated when there are new branches matching the filter.

there is commit ID but no branch id, branch id would help a lot to make more advanced custom commands!

When rewriting history via the journal (i.e. interactive rebase) runs into a conflict, it currently completely aborts (seems like "rebase --abort"). Like in native rebase --interactive I would like the opportunity to choose between 1) resolve the conflict and continue and 2) abort the interactive rebase.

If you check "annotated tag", you must fill out the Message field in order to press Ok.

If you do not check "annotated tag", then the Message field is grayed out.

So the checkbox is redundant with the message box. If you fill in a message, it should automatically become an annotated tag, and if you don't, then it shouldn't.

Large repositories, such as Qt's git://code.qt.io/qt/qt5.git contain multiple submodules. The normal workflow doesn't necessarily include all of those submodules. Allow the user to selectively enable only the submodules she desires.