Please try build #11091. It has splitted "Stash All" and "Stash Selection".

Yes, I also might have needed that some times.

Then I see only following options:

• duplicate all the information we show in the Log also to the modal interactive rebase dialog
• turn the interactive rebase dialog into some kind of temporary view and handle it with a mode of the project and log window where any command execution is prevented (because the interactive rebase command still is running)
• add a command to start the interactive rebase (which will fill a new temporary view with the selected commits similar to the Journal view), let you do the modifications in that view and then finally start the interactive rebase by feeding the information from the temporary view (or rejecting if the commits to be processed would have changed)

Honestly, neither of these options sounds right for me from the UX point of view.

No bad idea, especially when turning the Save Stash into a command that would execute without a confirmation dialog. (using always the default message). Maybe it would be useful to split "Save Stash" into "Stash All" and "Stash Selection" (which could show the dialog)?

Do you mean a Git-based issue tracker?

I wonder how this is handled by command line Git users.

Well, the problem in general is unrelated to GitHub Enterprise, but can occur for any in-house repository with proxy access to the internet. Just curious: can't the proxy be configured to also access the intranet servers?

Have you already tried to define an external tool?

SmartGit finds a certain amount of directories that are detected as repositories. What algorithm do you suggest for naming and grouping the repositories - please consider that only one group level is supported and other users might have different structures. Thanks in advance.

The compact view option only is available for read-only Changes views. The File Compare is designed to be freely editable.