At the moment in the bottom of the window comparison, which displays a one-line change to the code in horizontal view (top row from the left half, and the bottom from the right) both strings are displayed only if there is a 1-1 correspondence of lines and this is only the case if the entire changed block has same size on left and right. For example, in the following case, the top row appears empty in this view because it does not meet the requirements described above:

But this could be implemented by detecting appropriate "matching" lines:

The "Comments" List box Ctrl+Shif+8 shows a list of all comments.

This can be a quite long list. It would be better to show only comments related to the checked pull requests.

[1] (master)

[2]

[3] 

[4]

For years now, when I want to push commit #3 to a remote, I would do the following workaround:

1. Temporary create a branch on that commit without checking out and simply naming it "fddsfdsfdsfdsa".
2. Right-click on the branch from the graph
3. Push To > enter my desired destination branch name, e.g. "backup"
4. Delete the temp branch

As more of my colleagues are using this workaround, I wonder if the Push To functionality can be available when right-clicking on a commit, regardless of whether a branch is there or not.

We are just pushing a commit to a remote, so it shouldn't matter what the source branch is, therefore SmartGit can do the steps above behind the scenes (i.e. adding the temp branch if it's needed by the command line) if there is no existing branch?

When solving merge conflicts, it would be very useful if the diff view updated its colors when you change the view mode at the top (left+merge, all, right+merge, etc). So that you can see the diff visualization correctly.

For example, I get this in 3-way mode:

When changing to the left+merge mode, most of the green should go away, as those 2 files are nearly identical. Currently the colors are unchanged, which makes it difficult to view the diff, since it's colored "wrong" compared to normal diff views.

Some repositories have a really complicated history and it is hard to get all commits for a specific date:

I am on windows 32 bits. I want to use smartgit. I uses an old version in 32 bits. 

But impossible, "downlaod the last version or close"...

What's the point of having old versions?

I know it can be done from log, but it not easy and intuitive, also I want to ask new options that not available. 
First, please separate the index node and and working tree node. (should be always two nodes).
After I selected any two commits. it can be  local commit, index, working tree, regular commit, or commit in other branch,
It should give me an option compare and show me the amazing diff you have with these two commits. 
Also when I select one (of the two) commits as working tree, I will able to edit the changes to the working tree.
I added a picture to show you where I expected to see the compare option. (and not in other window as it today). 

Thank you for you time, I hope to see this features as soon as possible. 

For other users, please vote +1 for this.

================================================

After I write this request, I notice when I click two commits, it immediately show me the two diff between the commits.

But it as lack of seperate the index from working tree, and most important thing to do diff and edit to the working tree, when one of the commit is working tree. Also be nice if there will be option to compare in the menu I show, and it  will open a new window for that diff.It very useful for many compatrion in the same time.

Regards,

Tal Regev.

Currently, SmartGit (and your other tools) use non-standard search functions on macOS:

- Command-E does nothing

- Command-F changes the search string to whatever is selected

- The search text isn't shared with other applications, and is inconsistent, e.g.:

    1) Open Find, enter some common text (call it "A"), and search successfully

    2) Close the Wind window

    3) Make sure no text is selected and then open Find again: you'll see the same text you searched for before

    4) Enter some garbage text (call it "B") and Find; dismiss the "Didn't find" warning and close "Find"

    5) Use Command-G: it'll find the previous text ("A")

    6) Make sure no text is selected and then open Find again: you'll see the garbage text ("B")

It should use the standard search functions described in Apple's UI standards:

https://developer.apple.com/design/human-interface-guidelines/macos/user-interaction/keyboard/

- Command-E should set the shared search string to the currently selected text

- Command-F should open, showing the shared search string

- Changes to the search string should be shared with other applications

- Command-G should search with the shared search string; if it can't be found, then alarm (don't open a dialog)

- Have an option to allow wrap-around searches without prompting dialog

Love 'Smartgit', but when in the 'Dark' theme I find that the current

branch (in bold) does not really show up at all well against the other

(non-bold) branches.

I often find myself spending a few moments double checking which branch

I'm on. I'm running a 27" 4K screen.

Can I make a feature request to have the active branch in a different

colour (and not bold)?

Please add a way to quickly fast-forward merge multiple branches.  

In the "branches" view, if I have multiple branches selected, I would like to be able to right click -> fast-forward merge.  

If I right click on "local branches", "origin", or similar, I would like to be able to fast-forward merge them all.

My reason for this is when I like to keep a separate clone that doesn't have any of my local changes in it.  I use this to do merging operations that my have conflicts with my current working tree.  Or to have a clean copy to run comparisons with.  However, this gets out of sync with the upstream frequently since I'm not active in it.