Expert Software Engineer at a tech vendor with 10,001+ employees
Real User
Top 5
Feb 12, 2025
SourceTree is not a bad tool from a UI perspective. However, with Microsoft's innovation in tools like Visual Studio Code, which is open source, it is advisable to consider switching. Visual Studio and Visual Studio Code allow the fulfilling of both development and code management tasks in one tool, providing ease of use and broader functionalities. I would rate the overall solution a seven out of ten.
Coach Agile Architecture & DevOps at Sistemas Humanos
Real User
Top 10
May 23, 2024
There are some valuable features in SourceTree for viewing differences between commits and files, but I'm unaware of specific automation features. I would recommend SourceTree to other developers as it's a good tool. Overall, I would rate it a nine out of ten.
Program Manager/Engineer at a government with 10,001+ employees
Real User
Dec 3, 2020
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 tool. But then, you use it possibly like GitHub's doing with their GitHub Command-Line, where you get some convenience operators. I guess the trick there is just going to be maintaining Git compatibility and not having to learn a totally different workflow. In summary, this is a product that works for the case where I need it, but it's not something that I use all of the time. I'm not sure what it would take for me to use it regularly, or how I might better integrate it. I would rate this solution an eight out of ten.
Version Control systems help developers track and manage changes to software code, preventing conflicts and preserving history. These systems are crucial for collaborative development, ensuring a streamlined workflow and enhanced productivity.
Version Control Software, integral to modern development practices, assists teams in synchronizing work across multiple contributors by maintaining a detailed historical record of every change. Users describe increased visibility and efficiency,...
SourceTree is not a bad tool from a UI perspective. However, with Microsoft's innovation in tools like Visual Studio Code, which is open source, it is advisable to consider switching. Visual Studio and Visual Studio Code allow the fulfilling of both development and code management tasks in one tool, providing ease of use and broader functionalities. I would rate the overall solution a seven out of ten.
There are some valuable features in SourceTree for viewing differences between commits and files, but I'm unaware of specific automation features. I would recommend SourceTree to other developers as it's a good tool. Overall, I would rate it a nine out of ten.
I rate Atlassian SourceTree a nine out of ten. It has good data manipulation tools and is easy to use.
I advise others to evaluate GitKraken as well. I rate the solution a five out of ten.
There are other applications for the client-side that you can use to interface with Bitbucket. I rate Atlassian SourceTree a nine out of ten.
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 tool. But then, you use it possibly like GitHub's doing with their GitHub Command-Line, where you get some convenience operators. I guess the trick there is just going to be maintaining Git compatibility and not having to learn a totally different workflow. In summary, this is a product that works for the case where I need it, but it's not something that I use all of the time. I'm not sure what it would take for me to use it regularly, or how I might better integrate it. I would rate this solution an eight out of ten.