I am working on a rather large PR (refactoring entire code base for code style) – I started out with upwards of 800 commits. In order to properly squash them down to ~50 thematically sorted commits, I had to rebase interactively numerous times. I had to change my workflow substantially once I noticed that each of these operations required upwards of five minutes. The reason became apparent when I checked the load on the CPU: the git process was using only one process. Now I don't know if this is even within Syntevo's hand to change, but I love your client (it also didn't let me down with this very complex pull-request) and trust that you would do what you can to make it better :)

Keep up the good work!

syntevo feature request multi-threading.png

In the file-oriented view I can clearly see which remotes I have, modify them and configure them. Sometimes I need to checkout branches from more than one remote and have the ability to do something like "set remote".

With the new "standard workflow", these features have completely disappeared, and even though I like the new workflow, especially the tabs for each repository, I'm now forced to use the old file-based view.

Please fix this.

With "multi-commit/squashed view", I mean the entries in the Files tab when two commits of a branch are selected. The files are given with their cumulative changes. Please edit the header with the correct term.

RFE: Allow to cherry-pick from this cumulative view. In detail, that would be

1. create a new temporary local branch for the later of the two selected commits
2. squash the commits between the two
3. cherry-pick the selected files as it is implemented currently for single commits
4. delete the temporary branch

Please add support for full management of groups (folders) in the Standard Working view new tab window. Looks like I only have the option to remove a group or move to another group. 

I need to be able to create, delete, rename, and move groups in the Standard Working view.

Please add option to restore repo directory path in title bar. The repo directory path is included in the title bar in SmartGit 22.1.6.

I work with multiple workspaces and some of those workspaces include the same repos. It helps to see the repo path in the title bar to quickly identify which workspace I'm working in.

Can you support Amazon Linux 2 as a tested platform for SmartGit?

In another request I reported the Standard Window Drag&Drop feature added in SmartGit 23.1 Preview does not work on my Amazon Linux 2 (AL2) workspace. Received a reply that it works for Linux machines (Ubuntu, Manjaro - both with Gnome desktop). Our organization can only use AL2 workspaces.

I noticed the Standard Window view doesn't allow you to arrange the order of tabs. The Standard Window tab order follows the order in which the tab was opened. It would be helpful if I could arrange the order of tabs to my preference. 

Also can you add tab right-click menu options like "Move tab to beginning" and "Move tab to end". I usually have 4 or more tabs open at a time.

Would be nice to be able to open a terminal window with
smartgit's git (executable) dir added to path. On systems like windows
where i use the git packaged with smartgit one has to do this manually. And on system with other git installed would be possible conflict without (since might be different git version)

could possibly be alternatively done if
https://smartgit.userecho.com/communities/1/topics/270-flexible-toolbar-customization-be-able-to-add-any-custom-command-or-any-existing-action-examples

Optionally create new repo as bare

Useful especially when creating "backup" repo on removable medium like usb drive for

sensitive data. Possibly with new checkbox "bare repo" in the "add or create repository" dialog, which in turn adds "--bare" option to the "git init" command.

If I want to combine two commits, I don't expect having to do extra steps (as in: Having to equal out the commit messages)

Interestingly the command line git doesn't have this limitation. I can change `pick` to `fixup` (or `f`) and it'll delete the commit and move the changes into the commit above.