Following the move to ssh.bitbucket.org I updated my remotes and git known hosts to the new hostname.

When using the bitbucket hosting provider integration (with ssh) to clone a new repository, smartgit tries to use `bitbucket.org`. It should be updated to use `ssh.bitbucket.org`.

In the Graph/Log view, when the Filter field has regular expressions enabled, the filter should be applied to an internally concatenated string containing the commit's message and author.

This would make it possible to search for commits of a particular topic from a particular developer.

Example commit:

- Message: "Cleanup tracing exceptions"

- Author: "Thomas"

The regular expression  "trac.+thom" should match this commit.

I've paid for a licence, but I'm getting constant nagging at startup over macOS 27 being unsupported. I get it, but SmartGit works and this is just unprofessional nag-ware. No other apps on my Mac do this!

People without the perpetual right to upgrade will be FORCED to upgrade for no reason. Lets just have a one-time warning, and keep things professional.

Its a pity this otherwise superb product is resorting to nagware in this way. Essentially forcing everyone on macOS to buy a new licence every year.

`Sort by Refs (Numbers Reversed)` produces  the following order in the Log Window and the Working Tree Window:

2026/1231

2026/0101

2025/1231

2025/0101

However, in the Standard Window, the order is:

2025/1231

2025/0101

2026/1231

2026/0101

This seems inconsistent with the behavior in the other windows.

Hi!

Ctrl+Space in the commit message editor opens the file completion popup. I don't use this feature and would like an option to disable it.

The existing commit.fileCompletion.maxEntries setting appears to control the number of entries displayed, but setting it to 0 still displays entries, so it doesn't provide a way to disable the feature.

Could we get a setting to either disable this behavior or rebind it to a different key combo?

Please and Thank You!

When merging a branch which leads to conflicts, I often run into the problem that the conflicted files are spread across hundreds of rows in the Files view:

It is not practical at all to scroll though hundreds of files just to find the 5 conflicted files you need to resolve manually. The only practical option seems to be to sort the list by the State column, to have all conflicted files at the top.

That works fine, but after the merging state is left, the new sort order remains, and I have to change the sort order again to get the list sorted by relative directory & file name (i.e. a sorting order which feels comfortable for me).

As this is happening regularly, I'm constantly changing the sort order, which is annoying. I wish the sort order in the merging state is memorized separately from the sort order of the normal state. So every time I run into the merging state, files will be sorted by State automatically, and after leaving the merging state, sorting automatically changes back to Relative Directory & File Name (i.e. the sort order of *before* the merging state).

This would be a big quality of life improvement :-)

I often select to commits to see the differences between them. It would be great to have the path/commits between the selected highlighted.

When I open Conflict Solver, in numerous cases it overwhelms me with lots of unrelated changes because files were changed a lot. There may be only a few lines actually changed in the commit, but I see so many colorful lines showing the differences between ours/theirs and the merge result that it's difficult to understand what's going on without looking at the original commit. It's a confusing experience.

It would be great if all changes not relevant to the applied commit (as a result of cherry-picking, rebase, etc.) were somehow (optionally) highlighted. For example, irrelevant changes might be in muted colors.