User-friendly, easy to scale, and it helps to fix problems with our code repository
What is our primary use case?
We primarily use this for repairing a broken Git repository. I don't usually use it and others on the team, as far as I know, don't necessarily use it in the normal workflow, but it is pretty good when you have really messed up your repository. It lets you dive in visually and see what you've done. It's better than the command line tools.
Pros and Cons
"The most valuable feature is the ability to fix a broken repository merge."
"For everyday use, I am more comfortable using the command line interface, rather than using SourceTree."
What other advice do I have?
When people get into a jam, we tell them to use this product and try to see if they can solve it. That is if they weren't able to figure it out using the command-line tool. I guess that GitHub is trying to push into that too, where now they've now got a GitHub Command Line Interface, that's I think supposedly trying to mirror what the web version does on the command line, but still using Git on the backend. I wonder if that's something that SourceTree or Bitbucket might look at and say, how do they make a tool that works, still Git on the backend, but gives you a visualization in their GUI…