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.

If bracket pair colorizer is supported, it will be easier to analyze nested parentheses when comparing and reviewing files.

JetBrains IDE supports it as a plugin, and Visual Studio and Visual Studio Code also support it natively.

And it is also supported by GitKraken, a market competitor.

If this is supported, analysis will be much faster in file difference comparison.

The screenshot below shows the bracket pair colorizer supported by Gitkraken.

The bracket pair colorizer is supported in JetBrains IDEs if the following plug-in is installed.

https://github.com/izhangzhihao/intellij-rainbow-brackets

I found a very very strong drawback in your "Search for" form (appears not by hotkey or menu, but automatically as you type) in "Branches" View.
This form is absolutely incompatible with copy-paste!
Just try to find branch in "Branches" view using "Search for" and pasting required text from clipboard.
I tried several ways to workaround this strange behavior but everything did no work well.
If you type branch name manually - it works OK.
If you try to paste branch name or even part of branch name - it does NOT work.
Besides incompatibility of "Search for" with copy-paste from clipboard - it's also incompatible with standard text editing (for example, try to use left and right arrows to navigate in search text and edit it - your panel just disappears automatically).

My recommendation: allow user to make "Search for" permanent or show/hide it by explicit user request (not automatically - this works badly!) - at least it should NOT auto-destruct if I edit search text using standard text editing and it should work with copy-paste from clipboard.

Similar to `git diff <hash1> <hash2>` I want to select the first commit by searching in the log, mark it as "selected", then search the second commit, select it and do a compare. Alternatively, if a commit is selected, any commit can be clicked on to do "compare with selected". BeyondCompare has a similar behavior when selecting files from the Explorer.

For those of us who contribute actively to opensource projects based on forgejo(for of gitlab) platform, i.e. codeberg, it would be nice to have some sort of integration, i.e. referencing issues, query issues, list pull requests, etc.

Currently, when investigating a file (right click file/investigate), the Diff view :

only shows the diff between the selected file (New contents) and the previous version (Old contents).

It would be nice(r) if it was possible to select a previous version in the Navigation pane e.g:

and have that replace the Old contents so one could compare (i.e. not unlike the functionality from using the working tree view and doing it there - just focused more in the Investigate window as then one is looking at the one file rather than the whole commit)

It would be useful to see a name of the branch we're going to force-push.

When opening the file-specific log view and selecting two commits to show the diff, all the files modified between these two commits are shown. Since the intent is to look at the initially selected file, it would be much better if the filename was set by default in the filter, or maybe have an option to only show the logged file which would work across file renames.

When a repo's master branch has incoming changes and the repo is checked out to master, SmartGit displays the helpful down arrow indicator. But, if the repo is checked out to a non-master branch, there is no indicator for the branch-to-master status (as the indicators are for the checked out branch). To learn if a repo's master branch has incoming changes to update and rebase my working branch on, I have to click on each repo to review it. This requires reviewing the graph to find those commits and see how they align - is the branch missing commits from master.

The current product I'm working on has over 20 repos. To help this, perhaps an indicator on a branch in the Branches view when the branch is behind on its master branch?