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.
Used command line, git-tower and sourcetree. For basic things the command line is fine but I'm finding more and more I like the visual representation of what has changed offered in sourcetree and git-tower. Sourcetree seems to have a history of working great, getting an update and then performing really slow until another update. However it was still very useable when it was slow except on my largest projects but I could fall back to the command line if needed. A short while ago it got really slow and it would mess things up just trying to do a simple append to the last commit (on a project where I am the only person submitting). I was just too frustrated this time so I moved to a trial of git-tower. git-tower was fast and was a little easier to use (for example automatic stashing) and things in the UI were worded a little more intuitively . I would have paid the $79 to buy it but that was in USA dollars and I felt that was too high in my currency when developers in my country generally make 1/2 of developers in the USA. Before committing I noticed sourcetree had a bunch of updates including a major one that seriously boosted performance on my large projects and the bug on appending was fixed. Although things are a little more hidden in the UI for stuff that was upfront in git-tower, all the functionality I needed was there. I gladly pay for tools but I need to see the value and sourcetree does more and has no cost so I just couldn't continue with git-tower. See More
You can see the spinning wheel all the time. Some operations can be slow. If you know what you want (e.g., you want to touch a file, add it, commit it, and push it) you can do it much faster on the command line. However you're often not going to know what you want, so the visual diffs, for example, help massively. See More
SourceTree has three main repository views: file status, history, and search. File status view shows status of currently selected repo. It's split into two areas - file list and diff-view. History view tracks changes made to the currently selected repository. It's divided into three 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 giving access to git commands (such as commit, checkout, reset, stash, add, remove, fetch, pull, push, branch, merge, and tag). See More
Once installed, SourceTree will automatically try to look for and set up repos that are worked on. SourceTree will also detect if git-flow is used and what is the current development state as long as default git-flow branch names are used. The software tracks all relevant repositories in the bookmark's window. Repositories can be added to the list by creating new ones, adding a local folder, supplying a clone URL or integrating with remote services such as Bitbucket or GitHub. See More
It's possible to become overwhelmed with the information density presented in SourceTree. This is especially the case in history view, as it includes a lot of data presented in various ways. Though this is great for getting a comprehensive overview of everything that's happening in one place, it can take some getting used to. 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 the current state of repository. See More
SourceTree automatically splits the changes to be committed into chunks allowing committing (or discarding) each chunk separately. Furthermore, the user can even select specific lines. This greatly increases the flexibility of the user in that matter. See More
Powerful yet no coding skills requiredWebflow lets you build fast and fully responsive websites with your own designs and features without writing any code.
Free until you need a custom domainYou can fully build and design your website to explore the features without paying for a plan.
Interested in promoting your product? Contact us
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
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
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
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
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
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
Platforms:Linux, Mac, Windows
Issue Tracker support:Atlassian JIRA
Pro Features:Conflict Solver and Compare (freely editable); Pull Requests, Comments for BitBucket, GitHub and provider independent (Distributed Review add-on); Git-Flow; highly configurable views, external tools
Pull Request/Comments support:Atlassian Stash, BitBucket, GitHub, own Git server (Distributed Review add-on)
Leaving SmartGit idle for some time will launch project clean-up, which uses a lot of PC processing power, making it completely unusable until it finishes. This can be disabled from the options menu, but should have been disabled by default. See More
Using OAuth, you can connect SmartGit with your accounts in Github, GitLab, Bitbucket, or Stash and access the remote repositories there. You can then clone, fork, commit or push to your remote repositories from inside SmartGit. You can also view and manage pull requests for your open source projects from SmartGit. See More
Files can be instantly filtered by multiple factors: file name, recursive or not, unchanged, new, modified, ignored, assumed-unchanged, skipped, from submodules, renamed. This is an incredibly powerful and useful feature. The recursive option is particularly useful when combined with the folder tree view, allowing for a broader or narrower perspective to your changes as desired. See More
SmartGit has a rather clean and uncluttered user interface. All the most useful tools and information are displayed at all times or are otherwise just a couple of clicks away. All repositories are displayed in the sidebar and through a tabbed interface you can view various info about a specific repository (files, branches, branch graph, etc). The most used git commands like pull, push, sync, commit and merge are always available on top. See More
When the changes affect only a few characters in a line of code, the embedded difference viewers in the majority of competitors (such as SourceTree) show the whole line as removed and re-added. SmartGit highlights the characters that have been removed / added, so they are easier to read. See More
Using OAuth, you can connect SmartGit with your accounts in Github, Bitbucket, or Stash and access the remote repositories there. You can then clone, fork, commit or push to your remote repositories from inside SmartGit. You can also view and manage pull requests for your open source projects from SmartGit. See More
Usually a lot of products that are on MacOS and Windows let you use the same license for both platforms. Tower forces you to pay two licences if you are in this case (the unique benefit is a 20% of discount on the second platform). 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
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
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.