Git offers a configuration option named skipFetchAll (available since Git v1.6.6) that causes commands to process all repositories (git fetch --all and git remote update) to ignore remotes having this setting.

When fetching all remotes (either interactively from the Pull button with Fetch from all remote option checked, or from Background fetch), SmartGit should respect Git's skipFetchAll config option.

After locally reviewing many Pull Requests, the "Pull Requests" tree in the Log window gets longer and longer. So I'd like to clean up the tree by dropping their local data. But the "Drop Local Data" context menu item is not available if multiple PRs are selected, it's only available on single selection:

Support rebase and edit the first commit.

Support give an option to deal with date when rebase(or a global option).

This topic is about ignoring coloring sequences. If you want to see colors, vote for topic #1580.

Add a separate "Output (Terminal Mode)" window that is simply a read-only Git Bash shell to display the output of the last operation. It will not show the history like the original "Output" window does, only the last operation (if the last SmartGit operation is a group of git commands, then just show that group of commands).

Users can either display both windows, or switch between the two, depending on their needs.

Reason:  In the project that I'm working on, it is impossible to read the hook errors in SmartGit.:

I always have to open the shell, which is a pain:

Akin to Visual Studio and Visual Studio Code, it would be great if you could right-click on the SmartGit icon in the Windows task bar and choose from a list of recent and/or pinned repositories.

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: