Git it today
January 20, 2020

Git it today

Ray Smith | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Git

Git is currently being used for version control in our IT department. This allows us to not only keep various projects under source control, but also to work on many different features concurrently, and maintain many different versions of our software.
  • Git has a very small footprint and works seamlessly on all major platforms.
  • Git's branch management model is wonderful and simple, especially when compared to some other VCS tools I've used.
  • Git has no native GUI. This means that if you want a GUI you're reliant on third party software in addition to Git.
  • Git Repository configuration is done at the host level which makes it difficult to enforce certain requirements, like with Git hooks for example.
  • Provided a simple interface for developers to manage code.
  • Works seamlessly across multiple platforms.
The only other VCS tool I've used in production is SVN. In my option Git is a better option for several reasons. Reason one is simplicity, actions like reviewing changes, committing or stashing changes, and managing multiple feature branches is much easier with Git. The second reason I favor Git is the distributed model Git is built around. I can create and finish my own feature branches without needing someone else to manage the central repository for me. Lastly, Git is lightning fast and works cross platform.
Git has a great deal of documentation and it's very easy to figure out how to do what you need to do. That being said, Git has no customer support to speak of.

Do you think Git delivers good value for the price?

Yes

Are you happy with Git's feature set?

Yes

Did Git live up to sales and marketing promises?

Yes

Did implementation of Git go as expected?

Yes

Would you buy Git again?

Yes

Git is well suited for any file based scenario where source control is required. We mostly use Git for managing software repositories, but it would also be well suited for document version control. Anything that requires the modification of files and the potential need to roll back to a previous version is a good candidate for Git. The one scenario that in my opinion breaks this rule is database version control. With databases, we manage changes to table structure, functions, stored procedures etc., but I have yet to see good implementation of this with Git.