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.
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
The Linux Client is not updated regularly. Also it had a lot of crashes and lags while we used it in a project last year. Whileas the Windows Versions were performance wise ok the Linux Client was stuck all the time and Actions took almost forever. My personal opinion is also that you don't get enough feedback from the app while it's doing something. Perhaps the reason for the crashes was that we used it in a large project in an offline environment but I would have at least expected that the dev team is responsive and resolves the issues. But it was not. Flagged up the problems and never heard of them anything again. That's just bad support See More
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
Previously used Tower (reasonably happily) and SourceTree (inspired me to try anything else). Command-line native since '79. GitKraken makes the easy stuff a no-brainer, the tricky stuff straightforward, and the destructive stuff clearly marked and explained. It never gets in my way while freeing me from having to remember all the tricky little details of a tool that I use to manage all the tricky little details of my work. If you value devoting your available cognitive load to your goal rather than the tools you use to achieve your goal, give GitKraken a try. See More
Jeff Dickey's Experience
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
Really good product when it work, a nightmare when it don't 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
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
T2 has a good-looking interface and consists of 3 main views - services, repositories and repository. Services view for managing integrations with hosting services like GitHub, Bitbucket and Beanstalk. Repositories view for organizing local and remote repositories into folders and getting general overview about them. Repo view that consists of two main subviews: Working copy view shows modified files and their diff and allows wrapping up changes in a commit. History shows commits alongside metadata and projects file structure. Additionally, it allows performing various tasks such as merging branches via drag & drop, search allows searching by message, commit hash, author, committer and file and there's a quick open that allows fuzzy-searching for folder names. See More
Git-flow and Hg-flow provide a consistent development process by defining a strict branching model that is great for managing large projects. Sourcetree allows setting up and integrating into repos that follow this model. Clicking the Git-flow / Hg-flow toolbar button will give you access to actions for starting or finishing features, releases or hotfixes depending on current state of repository. See More
SourceTree has 3 main repository views: file status, history and search. File status view shows status of currently selected repo. It's split in 2 areas - file list and diff-view. History view tracks changes made to the currently selected repository. It's divided in 3 sections. The top section has a graph with progression of commits, branches and merges. The bottom section shows commit details, files changed and differences committed. Search view allows looking up commit messages, users, files changes, branches and commit SHA. There's also a toolbar at the top that allows switching between the three views as well as gives access to git commands such as commit, checkout, reset, stash, add, remove, fetch, pull, push, branch, merge and tag. See More
It's possible to be overwhelmed with the information density presented in Sourcetree. Especially in history view since it includes a lot of data presented in various ways. It's great for getting a comprehensive overview of everything that's happening in one place, but it can take some getting used. See More
This can be both a pro and a con, because the UI will change slightly depending on which repository type you're using. I'd say that it's more of a pro, though, because it helps you to either learn the command lines or instantly know what things are if coming from the command line. See More
User-friendly and feature-rich. Looks and feels great and it's completely free. See More
This feature is superior to the one that is implemented by SourceTree as it does not reset the file scroll view to the top of the file after each stage. If you do feature-specific commits after some time of development - it's very important to be able to easily compose the commit from different line-based changes. See More
does not support shallow cloned repo, sometimes rebasing does not work in the same way as command line 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
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.