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.

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!

In the file table, it could be great if the "filter by name" feature only would consider files visible without typing anything, not all files.

for instance if I want to see all .vhd modified file, I can unselect "unchanged files", and search for .vhd files.

currently smartgit will display all .vhd files even those that are "unchanged" whereas the "unchanged" button filter is activated.

Of course, you can also press CTRL + P and then enter the relevant subfolder to quickly see the desired branches. But unfortunately this is also very cumbersome if you want to merge the respective branch into your current branch:

1. You have to click into the branches-view.
2. You have to press CTRL+P and enter the subfolder you are looking for (and rememeber those names).
3. YouI have to select the desired branch. (Unfortunately, in this view you don't have the option to merge the selected branch with your current branch).
4. So you have to reveal the branch.
5. Finally you can merge the desired branch into your current branch.

Desired behavior:

I would like to define a filter for the branches-view and attach the filtered view as a separate tab in Smartgit (with a self-defined title). This way we could have multiple tabs for the branches-views (each with different filters and title).

Not only would this greatly improve the overview, but it would also reduce the number of steps that need to be taken:

1. Click into the filtered branches-view and select the desired branch.
2. Merge the desired branch into the current branch.