Git things done
February 12, 2019

Git things done

Cristian Bodnarasec | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Git

In our organization, Git is used by several departments for file versioning, collaborative work on the same source code, change tracking, branch merging, version comparison etc. Especially because we have distributed teams all over the world, we needed a reliable tool to achieve these goals, and Git was the natural choice.
  • File versioning - easy to see the history of the changes.
  • Collaborative work on the same source code -- by providing the ability to create branches.
  • Merging branches and comparing versions made easy.
  • It is free and open source.
  • Git is so popular that when hiring, it is easy to find developers who already know this.
  • To use Git at its full capabilities, one needs to spend some time learning it.
  • Command line usage may be an issue to developers used more with GUIs. For those, you may need to add a free GUI or purchase something like Bitbucket.
  • Merging code when there are conflicts can be difficult sometimes from the command line.
  • Git may have bundled in more features that it needs. Most people just need the basics: pull, edit, push, merge.
  • Using Git helped us having one central place for our source code, developed by a distributed team across the globe.
  • Due to its advantages, more departments in the company switched to Git from VSS or SVN. This resulted in the unified workplace and in having only one Git server for all teams(retiring the other servers and save money on the infrastructure).
  • Git helped us achieve our goal of having 2-week sprints with production releases (in most of the cases), from 3 or 4 weeks. This can be seen as having a 40% increase in the productivity of the software team.
Compared to SVN, Git has a decentralized approach which increases collaboration in the team by enabling the local stored branches. There is no need to be connected to the repository(via an internet link) to work and commit code. Besides the fact that the performance of Git is superior compared to SVN, it also has better support for merging and branches. A plus for SVN would be that it is easier to learn.
Git is suited for doing source code versioning of all-size projects, from small to large and very large. Does very well when you have distributed teams, as it increases the team's focus, collaboration, decreases the time needed for merging code and finding differences between file versions, and decreases the time needed to make a software release. Therefore, the time to market of new projects or new features is improved (any top manager's desire).