Here’s the Deal
Slant is powered by a community that helps you make informed decisions. Tell us what you’re passionate about to get your personalized feed and help others.
In Magit staging a hunk or even just part of a hunk is very easy. Magit also implements several other "apply variants" in addition to staging and unstaging. For example: you can also discard or reverse a change, or apply it to the working tree. See More
The UI is very straightforward, once you open it, you can browse your computer to find an existing git repository and open it in the app. Once opened you can browse commits and view remotes immediately. It also allows you to browse the files and preview them. There's also a commit view which shows past commit messages, as well as unstaged and untracked commits. See More
It's modern and beautiful, it looks clean and refined. It's simple: the most used features (pull, push, branch, stash, commit) are accessible in one click, and are the only buttons. The other features aren't in complicated menus nor in hundreds of buttons, but rather displayed when you right-click on something. It gives more space to the commits, i.e. the most important things. In fact, you can collapse or reduce the other menus/windows. It displays the current path (project, branch) on an horizontal (clickable) bar at the top. It's just a matter of taste but I prefer this to the traditional "tree" view. It has undo and redo buttons on the main window. It supports some drag-and-drop gestures (for example: drag-and-droping the local branch to the remote one pushes it). See More
Platforms:Windows, macOS, Linux
Pricing:FREE, $29/year for Individual, $49/user/yr for Pro, $99/user/yr for Enterprise
Integrations:GitHub, Bitbucket, GitLab, Azure DevOps, GitHub Enterprise, GitLab Self-Hosted, Bitbucket Server
Paid Features:Email Support / Merge Conflict Editor / GitLab & GitHub Enterprise IntegrationSee All Specs
I don't even know where to begin with this one. I think the simplest explanation must be this application is the result of a gifted digital graphics designer with a tragic lack of any awareness about UI/UX philosophy and best practices decided to create a Git GUI. Further complicating issues is an absence of a useful workflow within the interface; seriously not even the most interdependent git functions lead into one another, for instance invoking a Fetch on a remote offers no way to then execute a Pull/Rebase, etc.; you're just back where you started hunting through menus and buttons without labels for what you know needs to come next. I'm never going to forget about GitKraken though, because whenever I meet a rude developer on a project I never miss the opportunity to tell them how amazing this app is if you purchase the license, LOŁ See More
Peter J. Mello's Experience
Like most Electron apps, GitKraken has some memory-related issues. For starter, it requires more memory for an action than an equivalent non-Electron application. Although this should not be a problem most of the time for people who use machines with lots of RAM (after all, RAM is pretty cheap nowadays), it can have some issues when opening large repositories and there have been cases where GitKraken failed to open very large repositories or started lagging once they were opened. See More
GitKraken can be connected to Github, Gitlab, or Bitbucket accounts through OAuth. From that point onward most if not all actions that are related to these services can be done inside GitKraken. Things like: cloning or forking a repository, adding a remote, pushing to a remote repository hosted on these services can be done inside the app. You can even manage pull requests inside GitKraken for example. All pull requests for a certain branch for example are shown on that branch's graph. See More
A lot of care has gone into trying to make GitKraken as easy and intuitive as possible and it show. Every action is quick and painless with no more user interaction than necessary. For example, switching to another branch is as easy as a double-click on the sidebar. See More
No Ctrl-Click or Shift-Click for multi-selecting files. For example, if you have a few files you wish to delete, it is a slow process. You have to delete them individually; that is, right click a file then delete, right click another then delete, and so on. See More
In most cases of Merge Conflicts, users are stuck with auto-merge or manually resolving it by hand. This is because in the Free Tier, users can only (1) Keep File (ver 1), (2) Keep File (ver 2), (3) Auto-merge, or (4) Use External Merge Tool. In addition, using External Merge Tools is very limited because GitKraken (all tiers) restricts External Merge Tools to only those it managed to Auto-detect. It also does not support custom arguments for the External Tools. Modifying the merge output directly, or Selecting lines to keep/discard, is a Paid Feature. See More
I prefer using the CLI for all my git stuff, but if I don't want to drop into a shell, or background my editor (e.g. resolving complex merge conflicts), I sometimes use this plugin. All the power of your favourite editor, with all the functionality you expect from a git client. See More
Elias Van Ootegem's Experience
git blame only shows the last change (e.g. a variable rename), but how do you find the origin of the code? :GBlame to open blame window o on the relevant line to "git show" the commit select a diff line from a previous version of the file, and hit o to open it repeat 1 - 3, jumping back through history to find the origin of the line See More
Using git blame is as easy as :Gblame, and does the same thing, but should you need some more context, it's quite easy to see the entire commit that introduced the change. No need to copy-paste hashes, just hit enter. See More
I have used this in a non-Visual C environment for years. It has never let me down. See More
Help millions of people make better decisions.
Each month, over 2.8 million people use Slant to find the best products and share their knowledge. Pick the tags you’re passionate about to get a personalized feed and begin contributing your knowledge.