Compare GitLens and SourceTree 
- Reviewers mention that SourceTree has a user-friendly interface that simplifies Git operations, making it particularly appealing for small businesses. In contrast, GitLens is praised for its deep integration with Visual Studio Code, which enhances productivity for mid-market users.
- Users report that SourceTree's support quality is rated lower, with a score of 8.1, while GitLens shines with a score of 9.2, indicating that GitLens users feel more supported and valued by the development team.
- G2 users highlight that SourceTree's ease of setup is rated at 8.4, which some find slightly cumbersome compared to GitLens, which boasts a higher ease of use score of 9.3, suggesting a smoother onboarding experience.
- Reviewers say that SourceTree has a lower product direction score of 7.8, indicating some concerns about its future development, while GitLens users express confidence with a score of 9.0, suggesting a more promising roadmap.
- Users on G2 mention that SourceTree is particularly effective for visualizing branches and commits, but GitLens excels with its powerful code annotation features, allowing users to see who made changes and why directly in the code editor.
- Users report that while SourceTree is well-suited for basic Git operations, GitLens offers advanced features like blame annotations and inline commit history, which are essential for developers looking for deeper insights into their codebase.
Really helps to compare the code, giving insights to the whole timeline of even a single stack, line or even letter of code changed. Helped me in understanding and for peer review through it. Code versioning also becomes easy through it. Very helpful...
To work on this extension as a team, it is necessary to do it in a very coordinated way, as some changes can "overwrite" those of a colleague if not done properly.
Gives you a graphical interface for performing version control operations
To me the code merge feels not so intuitive and difficult to perform. I take backup and discard local files and get new files and do the merge manually.
Really helps to compare the code, giving insights to the whole timeline of even a single stack, line or even letter of code changed. Helped me in understanding and for peer review through it. Code versioning also becomes easy through it. Very helpful...
Gives you a graphical interface for performing version control operations
To work on this extension as a team, it is necessary to do it in a very coordinated way, as some changes can "overwrite" those of a colleague if not done properly.
To me the code merge feels not so intuitive and difficult to perform. I take backup and discard local files and get new files and do the merge manually.
