I use SmartGit for both Git and Mercurial, which is great: I have just one tool learn, and the same tool on Windows and on Mac. But, the commands and preferences for the two VCS are inconsistently implemented. For example:

The preference "Stash: Automatically save stash if Pull, Checkout, or Interactive Rebase fails because of local changes" works for Git but not Mercurial. Similarly, the Apply patch menu item uses the git apply command rather than the Mercurial import command even when pointing to a Mercurial repository.

SmartGit should be smart enough to know what sort of repository it is executing against and use the appropriate command, or tell us when that command hasn't been implemented.

Also, perhaps there needs to be separate preference tabs for Git- and Mercurial-specific preferences as there are some siginificant differences.

SmartGit allows you to create and apply a patches for Git, but not for Mercurial. Atlassian's SourceTree and the tool within Intellij IDEA have a context menu against log entries to create a patch from single or multiple commits.

Tools configured in the Preferences should work on the Log's File view in a similar way as in the main window

https://plugins.jetbrains.com/plugin/7566?pr=idea

Ability, when committing changes, to fixup a past commit (if there are no merge conflcts for subsequent commits)

Suppose I have committed 

A > B > C 

..in that order. I realize I missed something on commit B, if I want to fix it I have to introduce a new Commit D, and make an interactive rebase to move commit D so it becomes A > B > D > C and merge commit B and D (we often refer to part of this process as a fixup)

I suggest improvements to the smartgit interface to be able to perform this automatically. Note that this procedure is now facilitated by the --fixup param when committing as explained here

Idea : in the commit window, we already have a "select" menu that can help copy previous messages. Introduce a similar "fixup" select menu, which allows selecting a commit similarly to "select", but when a previous commit is selected this way, transform the "commit" button so it becomes a "fixup" button and actually performs

git commit --fixup=[selected commit ref] # Commit indicating a fixup
git rebase -i --autosquash [selected-commit-ref]~1 # merge fixup commit into broken commit

(ans similarly for the other button "fixup and (force) push"

References

https://stackoverflow.com/questions/3103589/how-can-i-easily-fixup-a-past-commit

At least as of v21.1.x the Working Tree window used alternating table row colors for the various files displayed. Could that be brought back in the current version(s), either as a setting or property of some sort? Or is there a way to do it already in the current version somehow?

Thanks,

Of course, you can also press CTRL + P and then enter the relevant subfolder to quickly see the desired branches. But unfortunately this is also very cumbersome if you want to merge the respective branch into your current branch:

1. You have to click into the branches-view.
2. You have to press CTRL+P and enter the subfolder you are looking for (and rememeber those names).
3. YouI have to select the desired branch. (Unfortunately, in this view you don't have the option to merge the selected branch with your current branch).
4. So you have to reveal the branch.
5. Finally you can merge the desired branch into your current branch.

Desired behavior:

I would like to define a filter for the branches-view and attach the filtered view as a separate tab in Smartgit (with a self-defined title). This way we could have multiple tabs for the branches-views (each with different filters and title).

Not only would this greatly improve the overview, but it would also reduce the number of steps that need to be taken:

1. Click into the filtered branches-view and select the desired branch.
2. Merge the desired branch into the current branch.

It could come useful to have totals for commit in Files view.

I.e. counts: total, renamed, changed, removed, added.