In the Graph pane, when there are too many branches on a commit the "less important" ones are grouped into an "X branches" button:

If you click on this button, it shows the extra branches in a popup:

But, there's no way to take actions on these additional branches; you must look for them in the Branches pane. Three things get in the way of manipulating them directly in the Graph pane: 

• If you right-click on the "X branches" button then a menu appears, but the "Check Out..." choice brings up a dialog where you must either create a new branch or work on a detached head
• As soon as you move your cursor off of the "X branches" button the popup goes away
• Even if the popup remained, it's unlikely that right-clicking on a branch name would bring up a menu and let you operate on that branch.

Proposal:

• If you right-click on the "X branches" button, show an actual popup menu listing the available branches
• Each branch name has a submenu giving the usual options for right-clicking such a branch

I'm trying to add hooks for the git-flow process, but they do not seem to be run when using smartgit.

I assumed smartgit uses gitflow-avh since the docs refer to it (here). So I added a pre-flow-feature-start hook to simply write to a file when a new feature is started (as described here). This works fine from the CLI, but with smartgit nothing happens.

When performing a git status . command in CLI, we can see submodules that have new commits and submodules that have modified content and/or untracked content

It would be great if SmartGit can show this in the files dialog. As it stands, I only see submodules with new commits which makes it possible for me to miss some submodule commits that I need to make.

In order to trigger a refresh for SmartGit, you have to close the app out and re-open it.

It would be nice to have a command via shell that can trigger a refresh. I have a script that I pull down all the repos and then it would be nice to have the refresh command triggered in SmartGit to refresh all the green arrows for pull.

I expected that "modify commit" would work like cherry pick without commit. In other words, it would rewind to before the selected commit and then stage but not commit the selected commit so that you can edit it. Then when you complete it should re-apply all subsequent commits. It would be great if "modify commit" did this, or there was another functionality which provided this workflow.

Duplicate: https://smartgit.userecho.com/communities/1/topics/552-interactive-rebase-should-show-commit-information

During an interactive rebase the main window is not accessible.Therefore it is not possible to access the graph and to get commit specific information (files which changed and file diff support). Therefore a large rebase process could be very annoying if only the commit message is visible / accessible.

I would be nice to have an option in the contextual menu of a commit to copy the "Full commit data", similar the "copy to clipboard" -> "Full data" feature in Tortoise Git (and Tortoise SVN).

It would be very handy if remote branch context menu had option to set the current branch's upstream. So user could create a branch, then right click the remote branch tile they want to track (which is usually there in the graph) to set the upstream.

The current Git convention is changing the principal branch name from master to main but SmartGit always create the principal branch named "master". If user want to use a different name to the principal branch a rename action is required after repository is created.

Please, add a configuration option to permit user configure any preferred name for the principal branch, then when a new repository is created, the preferred name is used, instead master.

Thanks for your attention and support,

When I create a local branch which doesn't track any remote branch yet and want to push the changes to a remote it would be nice if there was an option to select the remote repository and the branch.

Basically I would like to see this dialog, which is shown when I select "Push Up To..." in the branches view:

also when I select "Push Up To..." in the logs view.

The behavior of "Push Up To..." differs between the different windows:

Working Tree Window + Log Window: A dialog is shown where I can push the commits and SmartGit will push the changes to a corresponding branch on the default remote

Standard Window: SmartGit directly pushes to a corresponding branch on the default remote

I often work with local commits where I have stored some local settings which I don't won't to push to the remote repository. That's the reason why I sometimes don't won't to push the complete branch to the remote repository.

Best regards

Martin