I often want to split commit by files, without modifying content of files.

I guess it can be done much easier. 

* Selecting files from commit's file list, then just choose "Split Commit" context menu item.
* No need to specify which before or after new commit created into. It is easy to move new commit after created.

I have a repo which SmartGit fails to open. It looks fine when managed with command line tools, though. My first idea was to remove the repository from the SmartGit Repositories view and re-add it later, but the repo is missing a Remove item in the right-click menu. I don't want to remove the repo from the disk.

When finishing a release using git-flow, the current order of pushing to the server is `develop`, then `master`, then the tag.

For users with CI pipelines that start in the order that the pushes happen, it would be useful to be able to change the order so that the tag is the first pushed - that way the CI jobs for the tag can run first.

See https://groups.google.com/g/smartgit/c/LUB3hY1dT28/m/MgMTSg3-AQAJ for more details

Please support non-admin install. Inno Setup has /CURRENTUSER support on the command line but you need to update your install script to enable it.

Currently, the "If selected, the directories will be shown" only shows directories that contain changes unless the option to show unchanged files is also selected. Sometimes it is desirable to show the full directory structure, but only show changed files in the file list. 

Request is to either always show directories when the "show directories" option is selected even if they don't contain changed files, or to add a separate option to show unchanged directories or show unchanged files.

I do not why it changed to RED now. Before, it was BLACK color.

I think punctuations are unessential chars in sources, RED will capture our attenion!

I know i can change it in Preferences :)

Repro:

git init A
cd A && touch a
git add a && git commit -m "add a"

git branch develop

cd ..
git clone file:///path/to/A B
cd B/

git worktree add --track -b develop ../B-develop

cd ../A/
git checkout develop
echo '111' >> a
git add a && git commit -m "change a"

Open B, fetch manually (or let SmartGit Backgroud Auto Fetch), we can see green "<1" (picture1); Then at Branches View, we right-click develop branch and click 'Fast-Forawrd-Merge'.

OK, Now switch to worktree B-develop, we can bad thing (picture 2). 

I like 19.x, but after upgrading to 20.x, something changes.

First, at Log Graph, some commits have a square/blank label before their titles, esp. when I open some cloned projects from github, part of their commits are commited by Github(noreply@github.com) which are signed automatically. It cause signed commits and unsigned commits mix together, look ugly.

Please add one low-level properties to allow to hide the sign label.

I regularly copy the file name from the Files view which means using the context menu as Ctrl-c maps to copy the row data.  This request is to map Ctrl-c to copy the filename instead.

Since this request causes a breaking change, perhaps can create a low-level property with a list of options to map to?

Additionally, I always paste and then remove the extension, so my desired choice is map Ctrl-c to filename without extension.

Please can we have an option to disable the automatic selection of "Ignore as pattern" in the ignore dialog:

For the screenshot I have exactly one file selected and it is a C++ header. SmartGit defaults to selecting a pattern for all headers which means it is really easy (and has happened on a number of occasions at my company) where a developer accidentally ignores all new headers in a git project. Quite often this is only discovered during evening automated builds which fail due to missing files.

I would like an option to make the the default always "Ignore explicitly" forcing the user to think about whether they want to ignore the pattern. I would rather have very long ignore lists than accidentally not commit something that should not be ignored.

Some backgrounds: we have a number of tools that automatically generate C/C++ code within the source tree (for technical reasons) and we add these files explicitly to the ignore list for the various repositories.