It would be very handy if the Branches listed listed ORIG_HEAD in addition to HEAD for selection. So the user could quickly check ORIG_HEAD to see their previous state after commands like rebase. Thanks!

SmartGit should show an LFS indicator next to each file that *will be* committed with LFS, *before* the commit is done.

Ever so often, you bring in a new file type that should be handled with LFS. But without an indicator, it's not immediately obvious that you're committing such a file. Over and over, I accidentally put some 30 MB file into the normal repository, because it's some new executable or data file with a new extension, and I don't realize that this extension isn't already in .gitattributes. Then I realize the error, update .gitattributes, and going forward, this file type is now handled.

But the damage is done. I have half a dozen repositories that now have very large files on the normal Git side, which will never, ever leave the repositories.

SmartGit is hiding the LFS status too much. There should either be an indicator next to files that will be upload with LFS, or a column with the LFS status, that can be enabled.

The feature simply indicates whether the file name matches a mask in .gitattributes.

Please please please.

Thanks,

Per

When I have multiple staged files, but I select only some of them and press the button "Commit", I expect that the option "Local Changes" will be selected by default because I don't want to commit all staged files.

Sometimes, I forget to change the option, so SmartGit commits all staged files and it takes time to reset and re-commit.

At this time, the option "Staged changes" was selected automatically (https://smartgit.userecho.com/en/communities/1/topics/696-force-commit-dialog-to-always-select-staged-changes). It makes sense if the user selects nothing and only press the button "Commit".

Commit panel has very useful button for quickly commiting the changes in the panel

Consider adding Commit and Push button (as for the commit dialog)

When using CI, I very frequently make minor changes and immediately push to trigger the CI pipeline.  A commit and push button on this panel would save me much time

Sometimes when pushing, it often fails (Especially in Mainland China), I would like to cancel it instead of waiting for it.

1) Give back context menu items of non-head commits

It seems SmartGit 20.1 Preview 10 (2020-02-13) from changelog-20.1.x.txt updated:

```
- Log:
  Files: right-clicking a file in a non-head commit only shows now external tools that operate on that commit
```

Now it is really not easy to use `Reveal in explorer` or `Edit` command from files' context menu when we are
browsing commit histories or file log history. I also try to add my own external tool, but not show too.

Hope they can come back.

2) Show `Open in Git-Shell` from context menu of directories in Files.

It is complicated to use `Open in Git-Shell` in SmartGit,  this menu is always grey and unclickable unless
we focus on the **Repositories Window**. Hopefully it can be show at the context menu of directores
in Files.

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.

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.