git status lists "modified" files separate from "untracked", and does this for a reason.

SmartGit seems to add these two counts to one "changed" count.

When I committed all my modified files, I often have some untracked files (i have good reasons not to ignore or stash them), which always makes me think: did I forgot to commit something or are they just the untracked? and I need to check the files list.

If SmartGit would count them separate as git status does, that would save the hassle.

When working with several active release we usually develop the feature in the oldest active release and the merge things upwards to newer versions. 

For this usecase we need an option to ignore the whole merge in newer releases if it's not needed in here. Git provides this via `git merge --ours `

Please change the behaviour of the parsing of the results of the (pre-)commit hooks for SmartGit. One of our scripts echoes a "WARNING:" instead of the currently accepted  "warning:" as prefix. Therefore that warning is not reflected properly in the SmartGit-UI while committing. Please make the parsing case-insensitive.

It would be nice to have the "Commit" action in the context menu of the "Working Tree" item in the log view (version 18.2.+).

Currently, while using the Working Tree Window, if I have a repository with several submodules, and I hit to open the "Find Object" dialog, it only show the side bar repositories, but does not show any submodules from the opened repositories for selection.

If I would like to select some repository/submodule like "WrapPlus" on the `Repositories` view like this:

I would first type w, then, I would expect for it to first match the first repository starting with W like this:

But what it actually does, is to match the first submodule with `w` on the middle like this:

If I write more letters up to `write`, it still not selecting the repository I would like to select:

The only way for it to select the repository I want to is to type more than half of the repository name:

This is why I never use this feature because it is more easy to scroll with mouse than type almost the whole name.

If it matched first from the beginning of the word, I would just have to type `wr` for the correct repository to be selected, instead of `wrapp`

If you do not like to break the old behavior, a low level property to change this behavior would be extremely very welcome.

Add command-Line Options to open file in File Compare.

Something like

smartgitc.exe --blame C:\path\to\repository\path\to\file:400

but that shows current (non commited) modification on passed file like on double-click in main window

I'm primarily working with GitHub PRs where I squash review-adjustments before the PR get's merged. So Force-Pushing is part of my daily work. The additional warning popup is a bit disturbing there, as the keyboard-only navigation to the check-box is a bit cumbersome on macOS.

The actual master branch has a branch-protection enabled, so I wouldn't be able to force-push by accident there.

So, it would be great if I could disable that popup entirely.

GitLab provides functionality for creating nested groups of projects (subgroups).

Such subgroups correspond to multi-level namespaces.

In its current version (18.2 RC 2), SmartGit recognizes only the top-level namespace.

So, if "Project" is in "mygitlab.com/Group0/SubGroupA/Project.git", its "Namespace" in the window "GitLab Projects" will read: "Group0".

Instead, for the purpose of structure, I propose the namespace should read the full name of the namespace: "Group0/SubGroupA".

Otherwise, a different project, with the same name, in the same top-level group "Group0", but in a different subgroup "SubGroupB",

will not be distinguishable from the first one!

Compare:

That's exactly the awkward situation my team and I have run into recently.

Essentially, this means I can't use GitLab subgroups and create projects of the same name without running into confusion with SmartGit.

I hope I am not alone looking for the solution!

---

NB

This situation is not as farfetched as it may seem at first.

My team has been developing an embedded hardware product series S, which includes a number of separate hardware units (modules) M1, M2, M3,..., MN.

In terms of GitLab, each module is in a separate project of the same name. All modules make up the series - subgroup "S" of some other group.

Recently, series S is being completely redesigned and upgraded, both hardware- and embedded software-wise. At the same time, we can't abandon the old series S.

Therefore, we create a separate subgroup "S-New", with separate projects for redeveloped modules.

However, names of the modules should not change: customers are conservative with the modules names, because each unit name means a very specific industrial application area.

And here we are...

On the context menu on a stash in the log window, there are Drop Stash and Rename Stash, but not Apply Stash.