I recently discovered that you can nest groups in the Repositories view. This is an incredibly useful feature for us (as we work with over 100 repositories at a time).

I have a structure similar to the following:

ApplicationSuite (Group)
  + Apps (Group)
      + Repo One
      + Repo Two
  + Libraries (Group)
      + Repo Three
      + Repo Four
  + DataSets (Group)
      + Set One (Group)
          + Repo Five
          + Repo Six
      + Set Two (Group)
          + Repo Seven
          + Repo Eight
   + Repo Nine

The following enhancements (wishlist items) would make our lives even easier:

1. If you right-click on the parent group (e.g. ApplicationSuite) and choose "Open Repository", it should open all repositories in that group (Repo Nine) as well as all child groups (Apps, Libraries, etc) all the way down the tree. At the moment you need to expand all the groups you want to open the repositories for, select all the repos and the right click and choose "Open Repository"
2. Add the ability to see changed files in the current group as well as any sub groups. This would probably need to be an optional mode (controlled with (for example) a button next to the file filter text box) so that the current behaviour of only showing repos in the current group is still available. The behaviour and available options for the "expanded/recursive" mode would be the same as for a single selected group (being able to commit, stage, etc.).

Unlike ExamDiff there seems to be no possibility to mark files for comparison from the context menu of windows explorer. That would be a great extension.

Use case:

Select one file in windows explorer, use right click to open the context menu and then click on "Add to Comparison".

After that add another file to comparison using the context menu and select "Compare against xyz.ztx"

When doing support on a product, you're quite often confront to questions like "in which version does this fix/enhancement is integrated ?". When you got he sha, the "git tag --contains <sha>" command gives a good answer.

I added this as a new tool, but I think this could be useful to others, so maybe integrate this directly in Smartgit ?

E.g. to have all commits from a specific user highlighted.

When both windows are open, it's hard to distinguish one from the other, f.e. when switching between them by Alt+Tab:

It would be convenient if, f.e., one of windows icons were painted with some color:

Let's say that you have a bunch of old feature branches that you want out of the way but you don't want to delete them either.

So you go one by one renaming 'feature-123' to 'old/feature-123' ... tedious.

It would be nice to be able to do that for multiple branches by adding a prefix to all of them at once or perhaps something more sophisticated with pattern matching & substitution like this SO discussion https://stackoverflow.com/questions/45118089/git-rename-multiple-branches

For other Branch-related operations, vote for https://smartgit.userecho.com/en/communities/1/topics/1277-

Hi,

I would like to see a view that would list all PR's from all repositories that SmartGit knows of, very useful when your working in projects with many repos and many PR's to review

When groups are collapsed, there is no easy way to find an open repository (specially if one is using nested groups; see https://smartgit.userecho.com/communities/1/topics/291-highlight-group-name-of-opened-repository, too).

It would be great to have either (or all :-)) of:

* A function (menu entry, toolbar button, keyboard shortcut) to jump to the next open repository (invoking the action multiple times would cycle through open repositories)

* A list of open repositories in the window-menu

* Integration into "Find Object", e.g. either list open repos first or use a special command like "open" to list open repositories

git status lists "modified" files separate from "untracked", and does this for a reason.

SmartGit seems to add these two counts to one "changed" count.

When I committed all my modified files, I often have some untracked files (i have good reasons not to ignore or stash them), which always makes me think: did I forgot to commit something or are they just the untracked? and I need to check the files list.

If SmartGit would count them separate as git status does, that would save the hassle.