We can review, comment, merge, reject, retract Pull Requests in SmartGit, but we can't approve them yet.

I'd suggest a simple branch context menu entry and a Review menu entry for this: "Approve Pull Request". Ideally, if this user already approved the PR, this should change to "Unapprove Pull Request".

Another helpful improvement:

Add two buttons or options to the "Add Comment" dialog, to set  Approve or Needs work, analog to Bitbucket Server.

The buttons would have the same function as "Add Comment" button plus additionally set the Approve or Needs work flag.

The options can be toggled and would fire when "Add Comment" is pressed.

As a Needs work status should be explained, I'd limit this possibility to the comment dialog.

(Optionally) call prepare-commit-msg hook to customize the default commit message

Currently, each git stash shows up as a connected set of multiple sub-commits.

This is annoying because, when trying to see what files are part of a stash, you've got to click around to all 3 commits to see all the files.

What I would like is a way to collapse all three (visually, in the log) to a single line item that summaries the contents of all 3 commits, so I only need to look in one place.

Especially with Mercurial that have native support for it.

When using the Git-Flow Full the branch overview of the log would be better readable if the master and the develop branch are visualized like in the picture from https://nvie.com/posts/a-successful-git-branching-model/ e.g first lane always master and second always develop and then the feature and hot-fixes lanes dynamically.

If master or develop are not present (either because they don't exist yet or they have only old commits), the lanes should still remain unoccupied.

master  devlop  feature X

    O          |            |

     |           |           O

When having a feature branch with multiple commits and rebasing onto the development branch, conflicts may be hard to understand:

- it's should be clear at which commit the conflict has occurred, which commits have already been processed and which commits are left to process

- maybe the involved commits for the conflict can somehow be visualized

If Git writes URLs to stdout, they should be displayed as hyperlinks in the output window of SmartGit to open them in the default browser with a simple click.

This is especially useful when pushing new branches to remotes which response with an URL to open a new merge request, like GitLab does. Then you can just push a branch, click on the URL in the output window, and your merge request is opened in the browser.

Or as a second example, some remotes response with an URL to the new location of the repository if a repository was moved to another location.

This would greatly increase the clone speed for large repos that leverage LFS. More details can be found here: https://developer.atlassian.com/blog/2016/04/git-lfs-12-clone-faster/

This is the only part I don't manage inside of SmartGIT - I do those directly on the GitHub website, then once merged sync up again in SmartGIT and delete my local feature branch. :(