Currently if you make a branch, it follows the logic of default branch name, in my case `feature/` 

but in log, if you go to checkout a commit, the default local branch name does not follow the same logic, and just calls it 'branch'

Option to view multi-line commit messages in the Graph view itself. Would replace new line character with an actual line break. Multi-line messages tend to be rare imo but when you have one it's best to be able to see all of it. A checkbox toggle would make the feature optional.

Each individual branch has a checkbox in the Branches window that governs whether is is shown in the graph view.

When multiple branches are folded under a single entry in the (eg kokua has within it kokua/branch1, kokua/branch2, kokua/branch3 and so on) there isn't an easy way to show/hide all of the entries under there.

Right clicking produces a menu which includes Toggle, however that doesn't operate on the contents (I've bug reported that). The actual feature request here is to add a checkbox on the top level kokua entry so that show/hide can be done with just clicks and not needing to menu or click-hit space each time.

When the viewer or editor highlights parts of code that match the token that is currently at the editing cursor or the current selection is a super useful productivity aid and I miss it a lot in SmartGit.

So called "match margin" would be cool to have as well.

You can see how it work in a lot of editors, e.g. godbolt.org: move the editing cursor to a token or select text, notice how matches are highlighted and the locations of matches are indicated on the vertical scroll bar (the "match margin").

Would be extremely useful while looking at changes and blaming/investigating to quickly locate where in code things are used.

I often have the following scenario:

1. Current branch with non-clean working tree/index.
2. A branch I want to switch to with origin head pointing to the same commit as current branch and with local head pointing to some older commit.
3. When I switch to the target branch SmartGit asks for fast-forward merge and after accept I get lots of conflicts just because stashed changes are unstashed too early.

I suggest the following fast-forward merge for such scenario:

1. Stash changes.
2. Switch to the target branch and perform fast-forward merge.
3. Unstash changes.

In this case because stashed changes are applied to the same commit no conflicts occur.

It would be great to have such an option. This will help to not to forget to change default username and email for just cloned repository in "job" or "home" group and don't push commit signed with your private email to repository in "job" group and vise versa.

Tools like Visual Studio or Resharper often introduce lots of whitespace changes (mixed line endings, tabs), automatically.

Sometimes I want them, to cleanup the files, but sometimes I just want to commit the bare minimum diff to reduce noise.

I'd be nice to have an option to revert all the whitespace-only changes at once, either in the context menu, review pane, or file compare window.

This should follow the same pattern as the "ignore no/leading/all whitespace" radio menu in the file compare window, ie the lines that are highlighted or not would be the ones reverted, so I can preview the revert and know it's safe.

Some changes ( hacks, debug code ) should not be committed. Therefore, the modified lines of files should be inspected for possible "hack" markers and on commit, I want to be asked to check these files.

I'm doing a complex merge between two branches. The five files with conflicts let me use the Conflict Solver to compare the two source branches to the mis-merged file, so I was able to resolve and stage the issues. Now, though, I have 365 changed, staged files, and I'd like to review the changes. I can see how they differ from the previous version of the master branch, but there's no way to see how they differ from the merged branch.

I'd like to access the Conflict Solver, but it's dimmed out. Even if I un-stage the files, it's still dimmed out.

Please allow use of the Conflict Solver on any file during a merge. Ideally I wouldn't have to un-stage each file to use it, but ideally I'd also be able to edit the merged file; not sure how you'd make both options possible.

We can copy branch name but not a repository name (if that feature exists, I could not find it).  Please have Ctrl+c copy the highlighted repo name.

Working with many repos I regularly need to message someone with a repository name and branch name; copying the branch name works nicely but must type the repo name.