Currently, all pull requests are shown. It is quite messy in a large repo. It will be convenient for the users to allow us to filter the pull requests, or at least add an option to show the author's pull requests only.

When highlighting a commit in the log, I love the "on branches" sections of the commit pane.  However, it is currently only a comma delimited list that is definitely to read when it contains lots of branches or branches with long names.  I wish this section was more organized.  I would suggest a vertical bullet list.

When you close Smartgit and you have unpushed commits, Smargit git warns you that. However, it does not tell me where they are. When I have a repository with a large number of submodules or just a large number of repositories open, I cannot tell which one has unpushed commits because I do not remember when I did the commits and where. I can forget which submodule/repository I had committed when I had committed the changes several days ago.

Related to:

1. https://smartgit.userecho.com/communities/1/topics/1082-say-which-submodule-is-on-a-detached-head-state

In the following picture, the spacing between the avatar image/top text + commit title + commit body (message) could be smaller. The commit title is already bold, which should be enough to highlight it from the rest.

Suggested distance: (Photoshop)

References:

1. https://smartgit.userecho.com/communities/1/topics/1083-save-vertical-space-on-commit-window

Environment:-

One local repo encapsulating four similar upstream repos (master repo, fork of master repo, release repo, fork of release repo) containing the same code. The Master repo and its fork are where we work. The Release repo and its fork are updated each time a release is made. To mark a release I put a tag on two branches (we release two variants each time) and then need to send it upstream to all the repos so that they have it.

This is easy at the git shell level with git push <remote> --tags however it's one of the few occasions where SmartGit doesn't provide a better way of doing it. As far as I can see, SmartGit only allows one tag to be pushed to one remote at a time.

In Smartgit the operations on tags currently are Push and Push To... both of which only allow one upstream to be selected at a time, meaning that I have to locate and tick each of the two new tags and then do four Push/Push To operations to get the tags into all of the upstream repos. Actually it might be eight operations - I didn't check last time whether a ticked tag forms part of a selection and the whole selection is operated on or only the right-clicked tag.

The feature request:-

1) Right click on the Tags section of the Branches pane and have new options Push All to All Upstream and Push All To...

2) Push All To... should allow more than one selection

3) Right click on an individual tag - the Push To.. there should allow multiple upstream repos to be selected

4) Group operations in the Tags list - allow pushing of several tags by right click on one of a group that are ticked. Right clicking on an unticked tag would operate on that tag alone.

5) Expand the right click menu on a branch in the Branches pane to include Push Tags/Push Tags To...

Great client. My favourite for sure. I use its commercial version at work.

It would be great to have a md viewer like github/bitbucket/gitlab have.

We are not always able to freeze the develop branch in order to start a release, so we need to be able to specify the starting commit on the develop branch.

git flow command: git flow release start <version> <base>

git command: git branch <branchname> <start-point>

It would be really nice to have syntax highlighting for Go.

When working with submodules, in the parent repo you'll see the start/end commit of the submodule, along with the comments, but you can't see the actual changed in the submodule. You can open a log view of the submodule, but then you have to select the two commits; it's easy to filter for the first one using the SHA, but then there's no way to find the second one without unselecting the first.

What if you could filter for two separate SHAs in the "Filter" field? You'd then enter the two SHAs, click and command-click the two commits, and bingo: you'd see the diff.

Possible options:

• Have a separator character (probably not, as you'd want to be able to search through commit text)
• Allow extended regex (e.g. "(01010101|02020202)")
• ... something else?