Similar to this RFE : https://smartgit.userecho.com/communities/1/topics/1129-log-view-open-multiple-submodules-at-once

But for Repositories View.

It is something that I always missed something similar to what existed at SmartSVN.

Before submitting a code change to review, I usually try to clean it up and make sure the commits that make up the change make sense individually. During clean-up, I sometimes need to split commits, so the change could have ten or more commits waiting to be polished. At this time, it's sometimes difficult to keep track of which commit does what.

This work would be easier if commit graph would highlight the commits that affect a specific file.

What I have in mind is workflow like this:

1. Select a file in Commit / Files dialog.

2. Each commit that touches this file gets highlighted in Commit Graph.

The feature should be optional via Commit Graph hamburger menu.

Another variant of the same feature would add vertical lanes for the modified files in Commit Graph. Lanes would form a table with commits as rows, files as columns, and in each cell whether the commit modifies / deletes / adds the file. This would be more complex solution and might become cluttered if there are lots of files affected, so there should be a limit.

There should be following root categories:

• "Local Branches"
• one root category for each remote
• "Tags"

The explicit root nodes for each remote could also allow Remote-related operations (like in the Log window).

In macOS, when quitting SmartGit and then relaunching it, it remembers the last open repositories.

But this is not the case when closing the last SmartGit main window with the window's x button, and then relaunching it -

It doesn't remember the opened repositories, and just opens with all repositories closed.

This is very annoying!

I hope you can fix that.

I have several team members who infrequently make contributions to our team's Git repository.

The branching workflow we use means that they will almost always create a new branch for their contributions.

A continually reoccurring issue is that they do not remember to do a pull before they create their new branch, because they contribute so infrequently.

This obviously leads to people working on outdated code and has also caused a fair number of messy merge conflicts.

So it would be very nice if SmartGit had an optional feature to remind such users that their branches might be out of date when they are creating a local branch at a branch tip.

If the user...

1. right-clicks a branch tip in the 'Graph' pane, picks 'Check Out', selects 'Create local branch' in the pop-up dialog, and clicks the 'Checkout' button
2. or, right-clicks 'Local Branches' in the 'Branches' pane, picks 'Add Branch...', enters a new name in the pop-up dialog, and then clicks the 'Add Branch & Checkout' or 'Add Branch' buttons'
3. or, opens the 'Branch' menu, picks 'Add Branch...', enters a new name in the pop-up dialog, and then clicks the 'Add Branch & Checkout' or 'Add Branch' buttons'
4. or, presses F7, picks 'Add Branch...', enters a new name in the pop-up dialog, and then clicks the 'Add Branch & Checkout' or 'Add Branch' buttons'

...then a second pop-up dialog appears like this (where More Options is the same as the 'Pull' pop-up dialog):

I am imagining that 'Edit' > 'Preferences' would have a settings checkbox somewhere like 'Show pop-up dialog for optional pull before creating branch at a branch tip'.

Checking 'Don't show again (always Use Local)' would ensure that preference is unchecked.

This reminder pop-up dialog would be a massive help for infrequent contributors.

Please consider adding an EOL column that shows each file's used line endings (LF, CR, CRLF, native, mixed, etc.)

SmartSVN has such a column (disabled by default, IIRC), and I find it very useful to quickly identify files that are using the wrong line endings, as well as to identify tools that touched those files to correct their settings.

Steps to reproduce:

- open repo1 (double click it's name in a Repositories-panel)

- click "Recyclable commits"-checkbox in Branches-panel to show all recyclable commits in graph-panel

- open repo2 (double click it's name in a Repositories-panel)

- open repo1 (double click it's name in a Repositories-panel)

Expected: "Recyclable commits"-checkbox is turned ON

Actual: "Recyclable commits"-checkbox is turned OFF

Now you can right click a file in Files-panel and click "Ignore" to add the file to .ignore.
But it's not possible to add a folder to ignore.
I suggest to add option "Add folder to ignore". 
Or do not block slashes in pattern input textbox.
The reason why it is prohibited is unclear.

Even better - to add option "Ignore folder" to a folder menu here:

Parsing the `git rebase` command output and extracting the "Rebasing (x/y)` parts could be used to replace the infinite loading indicator with a progress bar in the status bar.

When ignoring whitespaces for line comparison, the diff view also ignores them in Java strings. Those should never be ignored.

I would consider that a bug.