When merge-squashing a branch back to develop or master it would be nice to include all commit messages from the branch inside the squashed commit. Sort of similar to the way Tower app does it. That way you don't lose the commit messages.

The SmartGit provides two ways to change highlighting scheme: first in preferences, second in edit window by clicking 'Syntax language' under view menu.

Both are not convenient enough in some particular cases. The first one is requires setting up for all formats you could have but not only standard. The second one requires too many actions.

Also in these approach there is no way to quickly change scheme from 'Changes' area. So the common way for 'Editor' window and 'Changes' areas expected.

The way how it can be improved to be more convenient:

1. Right click on diff panel -> Mouse over Syntax highlight -> Pick scheme. (Example from Sublime Text 3)

) (Two clicks one move)

or 2. Right click on diff panel -> Syntax highlight (opens window) -> Press '<Symbol>' for quick search-> <Symbol>scheme -> enter or Ok click.

or 3. Combobox somewhere in changes area with possibility to select scheme + Press '<Symbol>' for quick search

The handiest one is the third. The first one is on the second place.

The problem with showing the Log for only 1 branch is that when you see the tree, it's natural to believe that you're seeing the whole thing. So yesterday I saw that my branch, `development`, was on the latest commit but didn't have a remote branch. I tried pushing and pushing, but every time I'd get an error about a non-fast-forward push. I couldn't understand why this was happening, because there was no origin/development branch around. Only then did I realize that the tree was not complete...

If you want to invoke a tool on a file in a certain commit, vote for https://smartgit.userecho.com/topics/868

As already present in the main window.

I asked if we could open files from the log, but that's apparently not possible because they might have been moved since that commit, etc. we can only copy "relative path".

Then I thought I could sort by "Last Changed On", but that's the filesystem modification date, not the last time it was changed in the git history. If you check out a different branch, all files changed in that branch are marked with the current datestamp, rather than the last time they were modified in the history.

If you could show the last time they were modified as a column in the Files view, that would work.

Epic Games has released LORE, a next-generation version control system: https://epicgames.github.io/lore/

Once it matures, it is going to replace Git for many use cases. Please support LORE in your Smart{Git,Lore} product.

Lore does contain an embedded UI, but SmartGit is on a different level.

I want to jump from the Changes view to an external tool at that line. Need some way to get the line number to the external tool.

Group discussion about why:

https://groups.google.com/g/smartgit/c/TXuFWUypP7w/m/2DxzwxsuCAAJ

The workflow to add a worktree could be way simpler and faster.

Just right-click a branch → Add Worktree.

The current way, via the Repositories menu, feels like a clunky afterthought.

Current-workflow: copy-file → leave-SmartGit → file-manager-navigation → find-target-repo-directory → paste → return-to-SmartGit → stage-changes. Friction-heavy.

Proposed-feature: right-click-file → Copy-to-Repository → dropdown-shows-all-local-repos → select-target + choose-destination-path → automatic-transfer.

Result: file-copied-to-target-repo (new-file, no-history-attached) -- source-repo-unchanged, history-preserved.

Use-cases:

• config-file-sharing across projects (eslint, prettier, workflows)
• component-migration between codebases
• template-distribution to multiple repos
• cross-project-asset-syncing

Benefit: workflow-stays-in-SmartGit → no context-switching → faster-iterations → cleaner-mental-model

Current-workaround: terminal-cp-commands OR file-manager-juggling -- both break-flow.

This-feature → treats-repos-as-connected-workspace rather than isolated-silos.

The only thing that i find often inconvenient in SmartGit - the way conflicts are displayed and handled in Conflict Resolver.

SmartGit view:

JetBrains GitClient view:

The later has much more clear (and less scaring :) LOL)  picture of the conflicts.

Would be perfect if we are able to switch to yet another view on the conflicts that would be similar to the one on the second screenshot!

Thank you!