When comparing GitExtensions vs GitHub Desktop, the Slant community recommends GitExtensions for most people. In the question“What are the best Git clients for Windows?” GitExtensions is ranked 5th while GitHub Desktop is ranked 8th. The most important reason people chose GitExtensions is:
Instead of using HTTPS and authenticating every time they are pushing their code remotely, plenty of developers prefer to use SSH to communicate with the remote server and authenticate using secure key pairs.
Specs
Question Ranking
Pros
Pro SSH support
Instead of using HTTPS and authenticating every time they are pushing their code remotely, plenty of developers prefer to use SSH to communicate with the remote server and authenticate using secure key pairs.
Pro Great UI
GitExtensions has a simple layout, all usual functions being available without navigation menus. The branching and merging are clear and easy to follow.
Pro Git commands visibility
GitExtensions typically displays all commands that it carries out in a separate window. The user can also open the Gitcommand log (under Tools) and view the git commands as they interact with the program.
Pro Lightweight and fast
GitExtensions is a lightweight and fast application.
Pro Easy to use
Can be used as a Visual Studio plugin for developers who use it as their IDE, or as a standalone tool. Both are easy to use even for users not very familiar with git.
Pro Powerful commit screen
Staging/unstaging files and/or lines of code, ammending, overriding commit's author, commit templates.
Pro Easy to set up
Can either be set up as a shell extension, standalone tool of Visual Studio plugin, allowing developers to choose the way that suits their workflow best and is easier for them to get into.
Pro Open source
It's totally free
And its written and thought by developers who really know what you need as a developer. Open to contributions by everybody.
Pro Plugin API
There are several out-of-the-box plugins installed with standard setup. Additional behavior customization is possible with new plugins (written in C#).
Pro Very good stash support
Easy to save, view & pop stashes.
Pro Responsiveness
Pro Allows easy setting up of scripts to enhance productivity
Pro Useful plugins
Includes Gitflow, also has a delete obsolete branches feature which is very useful to get rid of those old branches that have already been merged. There are also other options to clean overall clutter in repositories.
Pro Simple, streamlined GUI
GitHub Desktop uses an extremely simplistic two-panel view. It's not capable of complex historical visualisations like other GUIs, but it is very easy to use (especially for git novices).
Pro Supports pull requests
In addition to being able to seamlessly and easily integrate with all of GitHub's features, it also supports forking and submitting pull requests on any open source project hosted on GitHub.
Pro Great GitHub integration
This is the official GitHub desktop client built by the GitHub team.
Cons
Con Not truly cross-platform
GitExtensions is not truly cross-platform. It can run through mono on UNIX-based systems but this does not work as well as it does on Windows.
Con UI may feel cluttered with too much information
The sheer amount of information that the UI displays by default may feel overwhelming at times, if not outright confusing.
Con Limited
Can't handle complex tasks. The Help Manual advises to use command-line Git instead.
Con Incomplete feature set
For e.g. Cannot do re-base, cherry-pick, commit chunks, stash.
Con Not free/libre
This application is proprietary, and thus cannot be modified or freely distributed.
Con Non-GitHub repositories are not fully supported
Since this is mainly a GitHub client, other repositories are not fully supported and with as many features and setting up a repo hosted anywhere else but GitHub is troublesome.
Con Buggy
Poster child for authors' programming ideology (FRP), likely the cause for the odd quirks and bugs it has.
Con No Linux support
There's no Linux version of this client.
Con Does not support multiple Remotes for a repo
Only allowed to assign one URL as remote. To manage/sync/fetch other remotes, use command-line Git instead.