My company has recently put in a new web proxy which man-in-the-middles all https traffic; it intercepts it, decrypts it, then re-encrypts it with a certificate that is signed by a local company authority. My understanding is that this is fairly common in enterprise environments.

This is largely transparent for web browsing, because the company pushes its own CA certificate to the PCs; but SmartGit (and its built-in git implementation) do not use this certificate store.

This means that SmartGit cannot connect to its update server and, more seriously, means that it cannot connect to any remotes.

I can probably work around the git problem by installing git myself and not using Smartgit's built-in version; but that is significant extra hassle on Windows, which I imagine is why there is a built-in version in the first place.

RFE: Allow users to edit the list of trusted root certificate authorities, or respect Windows's list. The latter would be far better, but would also be platform-specific.

This feature is available in the log windows under (Shift+F4), but only for a single selected file.

Regular compare (F4) works on a range of files.  This feature should too.

For those who have to always clean up feature branch history before merging (commit squashing, reordering, splitting, etc)  it would also be handy to have the "Fix up" option which basically is a "squash this commit with parent keeping parent message only). My co-workers constantly use GitUp for this kind of history rewrite thing, it's ugly but very fast. Personally I'd rather have only one tool.

gitk display a simple but great "text diff" of the content changed in files such as Microsoft Word.  This is very helpful when reviewing what was changed before committing and for review.  Please add this ability to the diff tool.

It could be useful to have a special line to show the cherrypick effect: the commit/branch from which the cherry pick started and where it arrived.

Here how it works in TortoiseHG:

The dashed line shows the cherrypick effect.

This is pretty useful with our Giflow Workflow.

I like to have a clean history in my repositories and thus I do lot of rebasing and squashing on feature branches. And there is especially one task I do *very* often in the exact same way: Amend (parts of) local changes to older commits of the current feature branch because there was something missing/wrong in an older commit which I want to fixup now. This is my current workflow to do this:

- Stage changes which should be amended to an older commit

- Commit index into a (temporary) commit (with a random commit message like "asdf")

- Using drag&drop in the Journal, move the commit down the history, right after the commit to fixup

- Select both commits in the Journal and choose "Squash" from the context menu

This works pretty good (as long as there are no conflicts), but requires lot of clicks/typing/dragging every time. If I'm not the only one who often amends to older commits, it may be worth to implement a feature to make this easier ;)

Such a feature could look very simple: In the Journal, add a context menu item called something like "Amend current index". Then one needs to just stage the desired changes, right click on an older commit in the Journal, choose "Amend current index", and SmartGit would do the whole rebase operation.

It would be nice if the repo status icons (the "orange up" or "green down" icons) can be repeated at the taskbar level.  We just need to add these arrows in the lower-right quadrant of the taskbar icon.

As a maintainer, I would like to know something has changed while SmartGit is minimized.

I believe some media players to this as well, indicating the play/pause state in the icon.

See also: https://smartgit.userecho.com/topics/655

TL;DR: If the Log window had a Repositories view, switching between repos is as easy as on the main window, and does not require finding/launching and switching to the main window to do so.

I understand the design decision to have separate windows for the different macro activities, so this request is an idea that will help a lot with usability in that design and is possibly a reasonable answer for those that want a single window.

I often work on large products and they often have over 25 repositories; this causes a lot of switching between repos.  I use one main window and easily switch between repos; occasionally I open a second or third main window but not usually.

I regularly open a log window when needed on a repo to review commits/diffs.  This is the usability problem - having to find the main window, select the repo, and open the Log window.

In pane Repositories, next to a repository (also true for submodules) the branch that is checked out is displayed, and the tooltip shows additional information about this branch.

When HEAD is pointing to a commit (no local branch present; 'read-only' checkout), the information displayed is very limited, being the commit ID and commit summary. Also the tooltip shows only few information.

Instead of

    Repository_name (short_SHA: commit_summary)

it would be great to have tag information displayed here if present, e.g.

    Repository_name (chronological list of tags)

and move the

    short_SHA: commit_summary

to the tooltip. The tags could also be added to the tooltip, one per line.

With this information I would be possible to immediately see for a repository using submodules which submodule versions are used (assuming that the submodule commits have been properly tagged).

Horizontal scrolling is bad, so it would be nice if this window allows word-wrapping, just like the Output window in Visual Studio.