In my OS by default, the scrollbars show like this:

Which is fine. However, when my mouse is near the last item, the scrollbar enlarges/become bigger and almost cover the last item 100%, making it very hard to select it:

I suggest allowing the scrollbar scroll down beyond the original limit:

So when the scrollbar enlarges, it does not hide the last item:

# cat /etc/os-release
NAME="Linux Mint"
VERSION="19.1 (Tessa)"
ID=linuxmint
ID_LIKE=ubuntu
PRETTY_NAME="Linux Mint 19.1"
VERSION_ID="19.1"
HOME_URL="https://www.linuxmint.com/"
SUPPORT_URL="https://forums.ubuntu.com/"
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
PRIVACY_POLICY_URL="https://www.linuxmint.com/"
VERSION_CODENAME=tessa
UBUNTU_CODENAME=bionic

@Marc Strapetz.deleted the topic Allow to select different file ranges with Ctrl with reason: No more reply from user.

But I have no idea about what that topic was because I cannot see it anymore. 

@Marc Strapetz What reply you are waiting?

How can I see the topic gain to reply to you?

In the Graph tab we can nicely interactively drag&drop commits. We can also squash neighboring commits. It would be nice if these two where quickly doable in one step, apart from the interactive rebase dialog. To me that is an often occurring use case as I often commit a small commit fixing an older unpushed commit. 

Currently, if a commit is dragged over a commit, as opposed to between two commits, the mouse pointer icon changes to 'prohibition sign'. How about if instead the prohibition sign, I could drop the dragged commit, squashing it with the destination commit?

At least for me, since the above use case is important to me, additionally even cooler would be if I could directly "commit" to any given unpushed commit, which behind the scenes would do a temporary commit, move it, squash it.

More often than not, a commit means to commit everything.  It often happens that I commit the single selected file rather than everything because I failed to first select all the files.  Or I am looking at the index and that is what I commit.

Maybe a warning "you will not commit everything, is that what you want?"  Maybe an alternate "instant commit" that picks up all the modifications.

In our environment we have two different main branches:
PROD/develop (for further development which should go into production) and ENTW/develop (for development which should go to testsystems only in order to go into production in about a quarter).

Would be nice to be able to switsh between GitFlow-Configurations to have the right prefixes to use the GitFlow workflow.

We would like to have a better integration of Pull Requests for feature-, hotfix- and support-branches.

In our environment these branches could be merged with Pull Request only (push branch and create a pull request).

So e.g. FINISH a feature-branch should not merge it onto local develop branch.

The names are switched in some situations where 'ours' actually refers to 'theirs' in two different dialogs.  You have to look at the git hash to know what is truly happening sometimes.  Just remove 'ours' and 'theirs', because it's a bad design paradigm, and often misleading.  Simply show the hash and the name of the branch and/or author where those hashes come from.

There's no way to put folder ignores in without editing the file directly, which seems unnecessarily effortful.  I seem to remember having this behavior once, maybe it was in SourceTree, but currently interaction with .gitignore is not ideal.

It would be extremely useful to be able to adjust the scaling on the fly, preferably with ctrl + and ctrl -.

I use SmartGit on a set up with multiple different resolution monitors and scaling, and it seems to be by chance which scaling SmartGit will launch in at any given time. I want to be able to adjust it manually.

Failing this, the software should scale based on which monitor I drag it onto. At the moment it is sometimes far too small for my 4k monitor, or far too large for my 1080p monitor, meaning I am restricted to using it on the monitor it is 'launched for' at any given time.

Currently double clicking a modified file opens File Compare.
I'd like an option (which I couldn't find) to set what happens when I double click, for example, open in the editor of my choice.