That's why Tower automatically and regularly performs a 'Fetch' operation in the background for me. Just a handful of pretty colors won't cut it.Ī Git example is that I don't want to check for new changes manually all the time. In my opinion, a graphical user interface has to provide some real advantages. And, with this knowledge, I can decide what the solution should look like - simply by clicking the files I want in the final resolution. I can clearly see which files clashed, how exactly they looked, who worked on them, and which commit introduced the changes. We've managed to find a visual way of presenting conflicts in Tower, which helps a lot in understanding the scenario. I had a hard time understanding what had happened - and an even harder time knowing what my options were. Dealing with Merge ConflictsĪdmitting this one is a bit embarrassing: I had always been a bit of a coward when it came to merge conflicts. That's when I love to have Tower open: the GUI guides me so I can easily fix my last commit, restore any historic version, revert a certain commit's effects, or discard local changes in my working copy. However, actually remembering all the different ways, commands, and parameters to achieve this tends to make my head spin. One reason why I love Git is that I can undo almost anything.

Let's look at some other pain points that developers face day after day. Cloning and managing repositories has become quite a bit easier. Even creating new repositories in your account can be done via Tower. Long gone are the days of wrestling with usernames, passwords, tokens, or URLs. You can access your repositories right from within Tower and clone them with just a single click: Since our recent update to version 2.3, Tower makes working with GitLab even easier. Solving such minor and major annoyances around Git has always been our motivation for creating Tower - a GUI client for Git that's now used by over 50,000 customers like Apple, Google, and Twitter. And yet it can be quite a drag: You have to find the repository you want to clone, get hold of its URL, remember your authentication credentials (and method!) and fumble them onto the keyboard…

You would think that cloning a remote repository was a simple process. And just recently, with the release of Tower 2.3, they work together more seamlessly than ever.

They share the same goal: to make working with code easier. GitLab and Tower, the popular Git client, have more in common than just 'Git'. This is a guest post by Tobias Günther, founder at Tower.

Tower git client