# Git Reviews **Vendor:** Git **Category:** [Version Control Software](https://www.g2.com/categories/version-control-software) **Average Rating:** 4.7/5.0 **Total Reviews:** 531 ## About Git Git is a fast, scalable, and distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Originally developed for the Linux kernel, Git has become the de facto standard for version control, utilized by millions of developers worldwide. Its distributed architecture allows each developer to have a complete history of the project, enabling robust collaboration and offline work capabilities. Key Features and Functionality: - Distributed Version Control: Every developer has a full copy of the repository, allowing for independent work and reducing reliance on a central server. - High Performance: Git is optimized for speed, efficiently handling large repositories with millions of files and commits. - Data Integrity: Every file and commit is checksummed and retrieved by its checksum, ensuring the integrity of the repository. - Branching and Merging: Git offers powerful branching and merging capabilities, facilitating parallel development and feature integration. - Staging Area: The staging area allows developers to prepare commits by selecting changes to include, providing greater control over the commit history. - Free and Open Source: Released under the GNU General Public License version 2.0, Git is free to use and modify, promoting collaboration and transparency. Primary Value and User Solutions: Git addresses the challenges of collaborative software development by providing a reliable and efficient system for tracking changes, coordinating work among multiple developers, and maintaining a comprehensive history of project evolution. Its distributed nature ensures that developers can work offline and merge changes seamlessly, reducing conflicts and enhancing productivity. By offering a robust set of tools for version control, Git empowers teams to manage their codebases effectively, leading to more stable and maintainable software projects. ## Git Reviews ### 1. Evaluating GIT **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Semiconductors | Enterprise (> 1000 emp.) **Reviewed Date:** February 14, 2017 **What do you like best about Git?** linux based commands, at the very same time would need Gui based tool **What do you dislike about Git?** Having a windows equivalent would be great where I can do operations through right click , command **What problems is Git solving and how is that benefiting you?** Source controling the code. ### 2. Git- Best Version Control System **Rating:** 5.0/5.0 stars **Reviewed by:** Munendra S. | Mid-Market (51-1000 emp.) **Reviewed Date:** January 08, 2016 **What do you like best about Git?** In software development, Git is widely used version control system. Using Git, it is easier to manage source code, collaborate. Git is faster and provides data integrity, flexibility. Easy rollback , branch creation and deletion. Merging different branches is smooth. Git is available on various OS. Also, Git provides private and public repos. **What do you dislike about Git?** Git is command-line based hence, takes time to master it. Merge conflicts are difficult to handle for large projects using only rebase. Reverting to previous commits can be tricky. Too many commands to do same or similar tasks. So, need to be well aware of each. **Recommendations to others considering Git:** Best available Distributed Version Control system. If you need to maintain source code or collaborate on a project, use Git. Git is flexible, has amazing features. It has low delay for push and pull operations. **What problems is Git solving and how is that benefiting you?** Git makes version control easier. Git is distributed hence parallel development is possible. Currently, We are using Git for controlling source code of software in development. Teams are finding easier to manage the code base using Git. Benefits: Rollback to previous commits Difference between versions Open source community help ### 3. Minutes to hop in, days to adapt, years to master **Rating:** 1.0/5.0 stars **Reviewed by:** Andrei D. | Software Developer, Internet, Small-Business (50 or fewer emp.) **Reviewed Date:** January 03, 2016 **What do you like best about Git?** The crowd praises the beauty of Git internals, but it is not improving overall user experience, not at all; worse — horns and tails of mentioned internals actually stick from most unexpected places introducing complexity that could easily be avoided. **What do you dislike about Git?** Poor design decisions led to leaking abstractions: * Design decision: "do not record changes, just store snapshots of working copy". Following that leaves no way but to detect file copying/renaming (using their contents' hashes). It is fine until user doesn't copy/rename _and_ change file between snapshots (refactoring, atomic commits — that sort of thing). Which leaves no way to Git but to *guess* what was renamed/copied to where, which (guessing) is so easy to trick. * Design decision: "only referenced version graph heads are meaningful". Following it introduces so-called "detached HEAD" state and situations like "I've contributed changes on top of a tag and now they are gone". **Recommendations to others considering Git:** Consider Mercurial first. It covers absolute most use cases you'll need with plugins distributed with it (all you have to do is to enable them), yet, though, not supported by various 3rd-party services as much as Git is. If you chose to stick with Git, well, it's another story: * Get some good and verbose workflow that covers as much "something gone wrong" cases as possible. Atlassian got nice comparison for you — https://www.atlassian.com/git/tutorials/comparing-workflows * Get used to Git internals' terminology that sometimes sounds just like something you've familiar with but isn't in fact: e.g. "object", "tree", "blob". You'll need it when you'll face issues which you most certainly will. * Fastest way to get working recipe is google "git how to " **What problems is Git solving and how is that benefiting you?** Contributing changes to projects in Git repositories ### 4. The best source versioning tool **Rating:** 5.0/5.0 stars **Reviewed by:** Cesar I. | CTO, Computer Games, Small-Business (50 or fewer emp.) **Reviewed Date:** December 30, 2015 **What do you like best about Git?** Git is very flexible and can be adapted to a lot of different kinds of workflows. There are several tools and services that compliment it but probably github takes the first price as it's by far the best online hosted git repository service. The way git handles branching, rebasing and remote repositories is very solid and gets the job done efficiently. Sharing code with others through a central server is easy (by using branches) and working on several features at the same time is a piece of cake. **What do you dislike about Git?** The command line could take a while to master and it's not for beginners. The concepts used are not very intuitive initially and it takes some effort to grasp them. Compared to mercurial, there's no feature that can match the ease of use of mercurial queues. There's also a lack of easy exporting revisions, change sets and other information to multiple formats, it's doable but not simple. I have to keep lots of aliases for common operations that should be a simple command but in practice they are multiple. Also I have to use several tools along side git for lots of tasks. **Recommendations to others considering Git:** It's better to start by using a UI to handle the repositories and a web based service like github for a central repository before diving into more advanced usage. **What problems is Git solving and how is that benefiting you?** Controlling source code it's central to any software development practice and git solves that problem like no other software could before (maybe only mercurial can challenge git in that area). ### 5. Coding? You need git. **Rating:** 4.5/5.0 stars **Reviewed by:** sarah s. | Theme Wrangler, Internet, Mid-Market (51-1000 emp.) **Reviewed Date:** April 26, 2016 **What do you like best about Git?** Coding? You need git. Not coding? You might still want git. Once you get in the habit of using version control, it's hard to go back. Create feature branches and switch between them super-easily. Undo and revert changes. **What do you dislike about Git?** Submodules are pretty weird to deal with. Sometimes I can't figure out merge conflicts exactly. **Recommendations to others considering Git:** Yes. Do it. Git is kind of odd to approach at first, but it has some major benefits over other version control systems, notably the ability to commit while offline. Branches are also pretty intuitive, and even merges aren't too tricky to deal with if you know what you're doing. **What problems is Git solving and how is that benefiting you?** Collaborating is a million times easier with git. It makes it super hard to lose your work. Being able to easily revert changes is a lifesaver. ### 6. My number one version control system. **Rating:** 4.5/5.0 stars **Reviewed by:** Ahmed A. | Co-founder and Developer, Computer Software, Small-Business (50 or fewer emp.) **Reviewed Date:** August 02, 2016 **What do you like best about Git?** The friendliest and most efficient version control. Very good community and adapted by large scale companies such as GitHub. **What do you dislike about Git?** Maybe it needs better documentation and tutorials for beginners. **Recommendations to others considering Git:** Spend time learning it before jumping directly to production. **What problems is Git solving and how is that benefiting you?** Managing different development projects. ### 7. Great DVCS **Rating:** 5.0/5.0 stars **Reviewed by:** Christian L. | Software Engineer II, Information Technology and Services, Mid-Market (51-1000 emp.) **Reviewed Date:** June 26, 2016 **What do you like best about Git?** Enjoy how powerful the software is to manage your source control. There is no single source of truth for the "central" repository. **What do you dislike about Git?** The learning curve is still somewhat steep. **Recommendations to others considering Git:** Try it out, it blows SVN, Mercurial, and TFS out of the water! **What problems is Git solving and how is that benefiting you?** Being able to reliably source control our code is essential to a software company. ### 8. Git removes all barriers to collaboration and code reviews! **Rating:** 5.0/5.0 stars **Reviewed by:** Aniruddh C. | Software Engineer, Internet, Enterprise (> 1000 emp.) **Reviewed Date:** December 17, 2015 **What do you like best about Git?** You can create feature branches, thus being able to work on multiple features (or versions of features) at once. This makes it easier to do code reviews, to apply other's changes, etc. It's easy to revert a commit, as compared to SVN **What do you dislike about Git?** It has a learning curve. The concept of branches etc are not intuitive to a new user. Rebasing is tricky, and conflict resolution is less intuitive than in SVN. **Recommendations to others considering Git:** Branching is key! Remember that Git is has difficult to use tooling on Windows systems, and that it has a learning curve. **What problems is Git solving and how is that benefiting you?** Git makes it easy for many developers to work on one project at once. I work on a number of distributed projects with numerous daily commits, and I've found that Git has allowed me to realize the benefits described above as well as being able to allow for more transparent code check-in processes. It also allows for a more stable codebase . ### 9. The best VCS I've encountered so far **Rating:** 5.0/5.0 stars **Reviewed by:** Alex P. | Senior Javascript / NodeJS Developer, Computer Software, Enterprise (> 1000 emp.) **Reviewed Date:** December 10, 2015 **What do you like best about Git?** - The ability to commit offline - LFS (Large File System) - The overall development process - The large community of users - The flexibility is great - If used properly, git is very powerful - Push to server - Commit hooks make it really easy to integrate within a Continuous Delivery system / Continuous Integration environment - the git stash command - tags **What do you dislike about Git?** - If the branching model you use is not the right one for your use case, things can get really complicated - Setting up a git servers infrastructure can be pretty tricky - The fact that when pushing directly to the server, the files can be seen as they are for a brief period of time. **Recommendations to others considering Git:** - Always read the full documentation, or as much of it as possible whenever using git. Also, always keep in mind that whatever problems you have encountered, most probably somebody in the community has already solved it **What problems is Git solving and how is that benefiting you?** - Avoiding monolithic commits - Manage the development process of very complex applications - When coming from other Version Control Systems (e.g: SVN), it is really easy to forget to push your changes ### 10. Need control during development? **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) **Reviewed Date:** February 04, 2016 **What do you like best about Git?** There was a time when source control meant copying one folder over another, merging changes manually, etc. That time is over with the use of Git. With a powerful engine, source control in every form is a bliss. Would it be forking a repository, merging branches, blaming on someone a change, it has the ability for it. **What do you dislike about Git?** The learning curve is steep at first, but fortunately it ends very quickly. As long as you don't actually have to use the command line, a number of gui tools exists to manage your sources. **Recommendations to others considering Git:** Take the time to learn the command line first, and make a couple dummy projects before hitting the real deal. GUIs are nice, but having some knowledge of the actual options is a plus. **What problems is Git solving and how is that benefiting you?** It is more of an everyday tool that can be widely used for pretty much everything now, and not just source code. We use it for shared documents reviewed and / or modified by different users to track changes within Word and Excel files alike. ### 11. easy to use **Rating:** 4.5/5.0 stars **Reviewed by:** Mudassir S. | Sr Java Developer, Computer Software, Enterprise (> 1000 emp.) **Reviewed Date:** October 06, 2016 **What do you like best about Git?** its easy to use and has lot of features which makes a developer enjoy working on it **What do you dislike about Git?** none of the features are disliked, no complaints **What problems is Git solving and how is that benefiting you?** none ### 12. It's Git **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) **Reviewed Date:** October 06, 2016 **What do you like best about Git?** Standard across the industry, countless integrations, and once you really understand it, world-class version control. **What do you dislike about Git?** Steep learning curve, and the occasional mess up that is utterly incomprehensible. **Recommendations to others considering Git:** Learn it. Seriously. **What problems is Git solving and how is that benefiting you?** The grunt work involved with being a sales rep. Take all the data-entry out of being a rep, and instantly sync your notes, meetings, events, contacts and much more into Salesforce ### 13. Neetu Bansal **Rating:** 3.0/5.0 stars **Reviewed by:** Neetu B. | Senior Software Engineer, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** October 07, 2016 **What do you like best about Git?** Easy check in and check out. Easily get the access **What do you dislike about Git?** Open source and sometimes it is difficult to store data **What problems is Git solving and how is that benefiting you?** Everything is good ### 14. The best, most flexible revision control system **Rating:** 5.0/5.0 stars **Reviewed by:** River W. | Senior Software Engineer, Computer Software, Small-Business (50 or fewer emp.) **Reviewed Date:** May 27, 2016 **What do you like best about Git?** Flexible and reliable. Excellent command line tools. Countless hosting options. Free to use. Well documented. Massive user and knowledge base. **What do you dislike about Git?** Steep learning curve. Somewhat unintelligent merges. 3rd party tools unreliable **Recommendations to others considering Git:** Read the Git book. It'll make all of the common tasks much more clear. **What problems is Git solving and how is that benefiting you?** Developer autonomy. Collaboration. ### 15. best thing ever df16 **Rating:** 5.0/5.0 stars **Reviewed by:** Vaibhav G. | Software Engineer-Full Stack, Internet, Enterprise (> 1000 emp.) **Reviewed Date:** October 04, 2016 **What do you like best about Git?** ease of use, easily integrates into other products **What do you dislike about Git?** need more features for git hub. but great otherwise **What problems is Git solving and how is that benefiting you?** source control ### 16. Git provide distributed environment to mamange source code **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.) **Reviewed Date:** June 12, 2016 **What do you like best about Git?** Branching and merging are easy Good Documentation Distributed environment Free to use i.e. open source **What do you dislike about Git?** I found sometimes that git not respond in case of large binary files (like logs file). **Recommendations to others considering Git:** In my personal opinion git is better than svn or hg. Its ease to use in term of use,share & manage code. **What problems is Git solving and how is that benefiting you?** We are 6 members in the team. We used git to work together and do the code review through git. ### 17. Full stack Web Developer **Rating:** 5.0/5.0 stars **Reviewed by:** Michael R. | Senior Software Engineer, Entertainment, Enterprise (> 1000 emp.) **Reviewed Date:** December 17, 2015 **What do you like best about Git?** It provides a reliable, structured, extendable means to save progress, version, and collaborate with others. **What do you dislike about Git?** There are some fringe cases that don't always function as expected. Sub-modules come to mind. **Recommendations to others considering Git:** Versioning Control Systems enhance all size teams, whether a solo developer or a team of 50. Git is a host of tools that has very little overhead, and is straightforward enough that you can get off the ground in a 5 minute crash course. **What problems is Git solving and how is that benefiting you?** It proves instant context while working with other developers. I know who last interacted with a piece of code, and why they made the changes they did. The level of integration is also massively helpful, as I can use my IDE addons and track changes on the fly. ### 18. Git is _the_ version control system used daily by Linux developers. **Rating:** 5.0/5.0 stars **Reviewed by:** Ján S. | Embedded OS Developer, Information Technology and Services, Mid-Market (51-1000 emp.) **Reviewed Date:** May 02, 2016 **What do you like best about Git?** The concept of distributed version control, it's implementation in Git and ease of use. **What do you dislike about Git?** I love to provide 360-degree feed-back but in this case there is really nothing I would mention. **Recommendations to others considering Git:** Do some interactive courses if you have never used git before. E.g. https://try.github.io **What problems is Git solving and how is that benefiting you?** Version control. Configuration files, scripts, source codes, ... ### 19. Great tool for code versioning **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.) **Reviewed Date:** October 07, 2016 **What do you like best about Git?** This is simply handsdown best code management tool I have used. Allows you to manage and maintain code changes over my globally distributed team with ease. **What do you dislike about Git?** The UI can be sometime hard to follow for someone new to the tool. **What problems is Git solving and how is that benefiting you?** Code management and ease of deploying and tracking ### 20. The way version control should be **Rating:** 5.0/5.0 stars **Reviewed by:** Stewart H. | Principle Engineer, Financial Services, Mid-Market (51-1000 emp.) **Reviewed Date:** January 28, 2016 **What do you like best about Git?** My favorite feature is its branching structure. On top of that, I like how malleable it is which is unfortunately in software developer, useful at times. **What do you dislike about Git?** GIT submodules, they never seem to work as intended or at least it would seem on the versions of GIT that i have used so far. **Recommendations to others considering Git:** Take some time to really understand the GIT model beforehand as it is different. A good research is https://www.codecademy.com/learn/learn-git **What problems is Git solving and how is that benefiting you?** Version control of our enterprise software. We have benefited from easier branching than subversion, etc and better tooling/community around the product. ### 21. Greattool **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Internet | Enterprise (> 1000 emp.) **Reviewed Date:** October 04, 2016 **What do you like best about Git?** Best collaboration tool for software development and especially distributed development. Opensource software depends on this, and now I can't imagine how to to achieve distributed development going without git. **What do you dislike about Git?** Help can be little better. Some of the commands are little complex **What problems is Git solving and how is that benefiting you?** Distributed development ### 22. git is a staple in my workflow **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Internet | Small-Business (50 or fewer emp.) **Reviewed Date:** December 09, 2015 **What do you like best about Git?** Git is very widely available and adopted. When it comes to version control git is definitely top of mind, and most developers have built up their own bag of tricks in getting the most out of it. In terms of my own personal use it has saved me from my own stupidity dozens of times. Having a snapshot of every state of my project over time is hugely valuable. Being able to `bisect` a code-base to find where an obscure bug was introduced is super valuable, and being able to check out a previous branch in order to rollback errors in production has saved a weekend before. **What do you dislike about Git?** As far as interfaces go, it's hard to break more rules than git does. The "checkout" command does like 3 different things based on the context of the command, for instance. These kind of weird inconsistencies make git very hard to learn, and create a lot of cases where I'm sort of blindly following instructions, rather than really understanding the depth and purpose of the tool. There are some nice front ends built for it, but they can't really cover the deep flaws that the tool has, so I've never stuck with any of them. Their sub-modules concept sounded interesting, but turns out to be kind of a wash. **Recommendations to others considering Git:** HG is out there, and from what I've used it's a good alternative. I wouldn't go proprietary though, and git has plenty of great benefits. **What problems is Git solving and how is that benefiting you?** Version control, code stability, communication with team mates ### 23. Best source control and collaboration tool **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Internet | Enterprise (> 1000 emp.) **Reviewed Date:** October 07, 2016 **What do you like best about Git?** seamless Source control and team collaboration **What do you dislike about Git?** Comments are sometimes confusing since they are tied to a particular commit **Recommendations to others considering Git:** Definitely use the tools suite like gitk and other graphical tools to understand branches **What problems is Git solving and how is that benefiting you?** Source control and collaboration ### 24. Version Control Couldn't be Easier **Rating:** 4.5/5.0 stars **Reviewed by:** Alec B. | Incoming Real Time Analytics Engineering Intern, Hospitality, Small-Business (50 or fewer emp.) **Reviewed Date:** November 19, 2015 **What do you like best about Git?** Git is fast and easy to use. On windows, I can easily log into my git server and clone the repository to my own hard drive. Do my work, edit as I please then seamlessly push it back to the repository and allow it to be updated. Git checks to make sure you pull before pushing, allowing for any user to avoid destroying a project with errors and conflicts. Git also allows you to go back to any previous push by any user and look at and modify the files when they were in that state. This allows for rolling back updates if fatal flaws are found or if a feature needs to be removed for any other reason. **What do you dislike about Git?** Windows lacks SSH keys and command line so Git programs must be installed and if using an outside server like github, some patience and time must be committed to setting up your PC to connect using Git. **Recommendations to others considering Git:** Research. It will take research to learn what commands you need. Knowledge of command line helps but overall just take your time, google and problems and work your way into using git for anything you may need. **What problems is Git solving and how is that benefiting you?** I can work on group projects anywhere and at different times as others but allow them to see what I have been doing and test what they have been working on as well with my own updated code. The real world application of building software in groups. ### 25. Great tool **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.) **Reviewed Date:** October 05, 2016 **What do you like best about Git?** Git is a great tool to use for development. Makes collaboration between developers a breeze. **What do you dislike about Git?** Merges can be troublesome sometimes. The automatic merge can be more intelligent. **What problems is Git solving and how is that benefiting you?** Writing Code ### 26. Best version control **Rating:** 5.0/5.0 stars **Reviewed by:** Aidan G. | Machine Learning Intern, Internet, Small-Business (50 or fewer emp.) **Reviewed Date:** January 19, 2016 **What do you like best about Git?** By far the most customizable and versatile version management system available. The feature set is massive and extremely useful. **What do you dislike about Git?** The large file handling is very poor. Sometimes the system can be confusingly setup. More warnings before extreme actions would be helpful. **Recommendations to others considering Git:** Great service, a must learn for any programmer. **What problems is Git solving and how is that benefiting you?** Version control is key to any dev team and git is hands down the best for the job. The work flow is fast, powerful and well understood across the development sphere. ### 27. The best distributed version control system I've ever used **Rating:** 5.0/5.0 stars **Reviewed by:** Eduardo S. | CTO, Information Technology and Services, Small-Business (50 or fewer emp.) **Reviewed Date:** December 11, 2015 **What do you like best about Git?** The learning curve is not big, It is simple enough to get started and powerful enough for more advanced usage. I love the ease of branching, rebasing and merging. **What do you dislike about Git?** The submodules feature is pretty lacklustre, I wish it was easier/more reliable. **Recommendations to others considering Git:** If you are coming from a no-distributed vcs like SVN or CVS, you can't go wrong with Git. If you are a user of another distributed vcs, like Mercurial, I believe the ecosystem around Git is the best selling point. **What problems is Git solving and how is that benefiting you?** We use Git on our day-to-day to all of our projects. Git has streamlined our development workflow. ### 28. source control review **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Human Resources | Enterprise (> 1000 emp.) **Reviewed Date:** October 05, 2016 **What do you like best about Git?** easy to learn and full of command linedd **What do you dislike about Git?** sometimes hard to understand some commands **Recommendations to others considering Git:** learn some tooltips online **What problems is Git solving and how is that benefiting you?** lead a team on source control ### 29. Powerful put not easy to use. **Rating:** 2.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.) **Reviewed Date:** August 25, 2016 **What do you like best about Git?** Multi options to control large get of people doing work, via branching. **What do you dislike about Git?** Not easy to use as a file tracker software, man ways to work with it, but not always easy read checkin to main repo details. **What problems is Git solving and how is that benefiting you?** Source control ### 30. Very happy with Git. Vastly superior to Subversion. **Rating:** 5.0/5.0 stars **Reviewed by:** Noah G. | Sr Data Architect, Mid-Market (51-1000 emp.) **Reviewed Date:** July 28, 2015 **What do you like best about Git?** My favorite feature of git by far is its ability to manage multiple branches and merge them in when they are complete. Also, 'git status' is beautiful in its simplicity and ease to generally know exactly what you've done. With 'git status' I can quickly determine whether all of my changes are staged and make sure that nothing I didn't want done got added to my commit. **What do you dislike about Git?** The command line tools are SO powerful that I often find it difficult to know exactly how to accomplish certain tasks. Specifically when trying to revert a bad commit, do I use 'revert' or 'reset' ? Actually what is the difference between 'reset' and 'revert' ? **What problems is Git solving and how is that benefiting you?** Git was obviously developed with the modern development cycle in mind. At my current workplace we were using subversion when I first started there and we very quickly outpaced its capabilities. Trying to run two separate branches and then merge them back together was tedious and fraught with difficulty. With git, that workflow has become easy peasy. We now have 5 active teams regularly working across at least 4 different repositories. Our development team successfully launches code to production multiple times a day with few hiccups ever. ### 31. The leading SCM tools **Rating:** 5.0/5.0 stars **Reviewed by:** 佳亮 . | Mid-Market (51-1000 emp.) **Reviewed Date:** June 07, 2016 **What do you like best about Git?** Git provides amazing SCM features such as rollback, merge and commit history. **What do you dislike about Git?** Perhaps its massive amount of command, which is kind of hard for beginners. **What problems is Git solving and how is that benefiting you?** I've used Git for most of my personal projects, including coding and documents. ### 32. Powerful with a learning curve **Rating:** 4.5/5.0 stars **Reviewed by:** Seth K. | Lead Web Developer, Internet, Enterprise (> 1000 emp.) **Reviewed Date:** July 22, 2015 **What do you like best about Git?** Git's branching model is the best of the version control systems-- lightweight branches that can be switched and merged at will. It's also very fast and diskspace-light because of the way it stores only incremental changes for each commit. It's easy to move along the commits in your branch if you need to return to an earlier point in history, for example to create a new hotfix branch. **What do you dislike about Git?** It's evident that git has grown organically-- there are lots of warts. There's little consistency between commands, errors can be cryptic, and the documentation isn't great. Using a git client like SourceTree or Tower abstracts a lot of the pain away, though. For the most powerful commands you'll still need to get comfortable with the client. It can be easy for new users to think that they've lost commits during certain operations like rebasing. We've had to train people not to freak out and start resetting their branches if merges go wrong-- git still has your commits, they're just detached from the tree. **Recommendations to others considering Git:** Understand the branching model. Challenges: https://try.github.io/levels/1/challenges/1 Learning resources: https://help.github.com/articles/good-resources-for-learning-git-and-github/ GitHub: https://github.com/ **What problems is Git solving and how is that benefiting you?** Git makes it easy for parallel development to occur. Moving from a centralized VCS, we've found that it's easier to work on long-running projects that eventually get merged in, and a pull-request model makes bringing changes into the master branch far less onerous. ### 33. Fast, lightweight, and portable version control system **Rating:** 4.5/5.0 stars **Reviewed by:** Terry N. | Assistant Programming Instructor, Higher Education, Mid-Market (51-1000 emp.) **Reviewed Date:** July 21, 2015 **What do you like best about Git?** Git alone is incredibly simple to set up in no time at all. All you have to do is install it, open up a command prompt, make a new folder, and type "git init" to create a repository. Committing requires that you specify a name and e-mail address to identify with, and with that, you'll already have a repository that's ready to go. Forming, closing, and merging separate branches of development is a breeze. While Git itself is a complete tool, it is also capable of interfacing with third party tools like P4Merge for handling diffs and merge conflicts. **What do you dislike about Git?** While it is capable of storing and managing different versions of binary assets, the size of the repository will begin to grow at an alarming rate as more iterations or assets are stored. Other solutions such as git-fat, Dropbox, or sheer symlinks simply off-load the binary assets onto external storage services, such as Amazon AWS. The flexibility and efficiency afforded by not having all actions checked against a server can also be a downfall: there is nothing stopping you from accidentally editing the same file as another user. **Recommendations to others considering Git:** Originally written (and still partially maintained) as a collection of shell scripts, Git should be relatively simple to anyone who has experience with working with Linux via the terminal. If you're not interested in hosting repositories off-site via Github or Bitbucket, you might want to look into Gitlab as a fast and simple solution for easy yet granular control over who has access to what internally. **What problems is Git solving and how is that benefiting you?** Git helps facilitate versioning systems for our various projects at the school. Individuals are encouraged to practice source control habits by creating repositories for their own projects. When put into groups, they tend towards Github as a centralized host for a repository that they can all access from home or work. It serves as a great stepping stone in not only helping students be conscious of how they are organizing their project, but also in forming an understanding of the purpose of source control before moving on to other solutions such as Perforce and Git. ### 34. The best source control system I have ever used **Rating:** 5.0/5.0 stars **Reviewed by:** Franky C. | Senior Server Developer, Marketing and Advertising, Mid-Market (51-1000 emp.) **Reviewed Date:** July 21, 2015 **What do you like best about Git?** Git is decentralized and distributed which allows great flexibility while always maintaining a backup copy with every instance of the repository. Extremely fast and secure with strong support for non linear development, branching and workflows that include software development best practices such as code reviews, approvals and code discussions. **What do you dislike about Git?** The learning curve can be challenging for some, specially if used to other version control systems, such as Subversion or SourceSafe but once integrated in the flow it is really easy to handle. A Linux/iOS background is great to get into the Git flows, specially using the terminal/command prompt commands. **Recommendations to others considering Git:** Start using it, even if the learning curve looks to sharp at first. Once into the flow wont be disappointed. **What problems is Git solving and how is that benefiting you?** Git is the most used version control system in the company and when combined with other tools such as the Atlassian suite (Stash / Jira / SourceTree) provides a very strong development environment to support continuous development and integration through out the full development cycle, no matter what programming languages or technologies are used. ### 35. Git **Rating:** 5.0/5.0 stars **Reviewed by:** Justin E. | Team Lead, Engineering Response Team, Computer Software, Enterprise (> 1000 emp.) **Reviewed Date:** July 21, 2015 **What do you like best about Git?** Git is an extremely powerful version control system with a great ecosystem of tools around it. Once comprehended, the model used by Git is fairly complete and covers the expected set of operations in a modern version control system. Git is highly performant even on large repositories. **What do you dislike about Git?** The onrap to Git is pretty steep. This has become a bit of a cliche, but it is true to a great extent. While GUIs like GitHub and SourceTree can help, onboarding a new collaborator to a Git-based project can be difficult. While there is a decent set of documentation available, the fact that Git is so flexible means that teams end up writing some of this themselves (or should do this) as Git in the abstract and "Git as our team uses it" may be signficiantly different. **Recommendations to others considering Git:** You really need to look at the whole ecosystem around Git. While Git is a Distributed Version Control System (DVCS), most usages actually use a hub-and-spoke model where there is a central repository. Are you going to use GitHub? GitHub Enterprise? BitBucket? Stash? Gitorious? And what kinds of GUIs are you going to use? Built into IDEs or standalone? Assume that new users will primarily use a GUI and expererienced users will use a combination of a GUI and the command-line interface and plan accordingly. **What problems is Git solving and how is that benefiting you?** Primarily we're talking about highly distributed enterprise software develpoment. Since adopting GitHub Enteprise in particular as a hosting solution, however, I have seen Git be adopted in a variety of smaller-scale projects just because once you use it on a large project, you really want to use it all the time. ### 36. #1 version control software in the market **Rating:** 4.0/5.0 stars **Reviewed by:** Haisheng H. | Product Team Manager, Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** March 18, 2016 **What do you like best about Git?** Git is the de facto standard version control software after VSS, CVS and Subversion. **What do you dislike about Git?** Some 3rd party GUI wrappers/shell extensions are needed in some cases. **What problems is Git solving and how is that benefiting you?** I talk to Github with Git. ### 37. best vcs so far **Rating:** 5.0/5.0 stars **Reviewed by:** Pavlos V. | Senior Developer, Media Production, Small-Business (50 or fewer emp.) **Reviewed Date:** February 02, 2016 **What do you like best about Git?** it's fast, feature-full, and easy to use (see dislike part). **What do you dislike about Git?** it's not the easiest concept in the world to grasp at first, but you can grok it soon after starting using it. **Recommendations to others considering Git:** git is the best version control system so far. **What problems is Git solving and how is that benefiting you?** versioning, and having different branches to deliver to different people. ### 38. Git is a life changer **Rating:** 5.0/5.0 stars **Reviewed by:** Sergio R. | Software Development Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** July 14, 2015 **What do you like best about Git?** Branching and merging are first class citizens - You can create and switch between branches very easy, branches are cheap since they're just "pointers" to commits, rather than copying files like in SVN. Huge community and healthy ecosystem - Git community is very vibrant and the project has a lot of support from the community which means that it's always improving and adding new features. There are code collaboration tools that will make your life easier if you want to use it in your team/organization, e.g. GitLab, Github, BitBucket, etc. Performance is *good* with large codebases - Performance is fine unless you have a very huge codebase, see Facebook use case http://thread.gmane.org/gmane.comp.version-control.git/189776 Distributed - You can commit offline to your local repo and push to the origin once you're back online. Others can contribute to your repository too. **What do you dislike about Git?** - Documentation needs improvements to make it easier to understand for humans :) - Big learning curve, especially when you want to learn about advanced operations - Too many ways to do the same thing (this is maybe an advantage, but it can be confusing for people new to Git) **Recommendations to others considering Git:** Take your time to learn the basics before you switch, make you sure you understand the basic workflow and the terminology, this will make your life easier when you're looking for help. **What problems is Git solving and how is that benefiting you?** The development velocity improved when we switch from SVN to Git, being able to quickly create branches for features and hotfixes was one of the biggest benefits we get from Git. In other words, it helps you to be agile. ### 39. sweet **Rating:** 4.5/5.0 stars **Reviewed by:** Kumar J. | Software Test Engineer, Human Resources, Mid-Market (51-1000 emp.) **Reviewed Date:** July 28, 2015 **What do you like best about Git?** i love being able to review a developer's commit history to track changes. this isn't anything earth shattering. but compared to microsoft's tfs, git is orders of magnitude easier to navigate and use. generating compares between commits or branches is dead simple. I also like having the option of using the command line if I don't feel like using the web UI or visual studio. **What do you dislike about Git?** I haven't found anything about git that I dislike. **Recommendations to others considering Git:** try it. I haven't found any limitations from using git. **What problems is Git solving and how is that benefiting you?** I'm a software tester, so my main focus for using git is to have a place where I can pull in the latest changes that a developer has committed. Additionally I use git to check in my automation, Finally I use git to do code reviews. All of these processes are a breeze with git. ### 40. Git is fantastic **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.) **Reviewed Date:** December 09, 2015 **What do you like best about Git?** Git is the industry standard. Everyone uses it. In all honesty when I first starting using it I was confused, but since everyone uses it there is a lot of documentation online and lots of people to give you tips so it's pretty easy to get the answers you need. Mainly my favorite thing about it is that it exists because version control is so important. I haven't tried any other alternatives and I don't think mot people have, which speaks about how good git is at what it does. I've never wanted anything else from it or thought of switching. **What do you dislike about Git?** Some commands are a little strange at first, but you get used to it very quickly and everyone uses it. **Recommendations to others considering Git:** Use it. **What problems is Git solving and how is that benefiting you?** Version control. Super super useful. Everyone who is developing any code related project should use this. ### 41. A wonderful Distributed Versioning system. **Rating:** 5.0/5.0 stars **Reviewed by:** Kyle C. | Software Engineer II - Global R & D, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** May 26, 2015 **What do you like best about Git?** Wow, best? that is tough. Fast, cheap branching? Distributed Workflow? speed? there are too many to choose from. I have to say that after using a number of older versioning systems git is a breath of fresh air. fast enough that you never think about it. branching so cheap you can create a branch for every feature or spike. a must have for every developer. **What do you dislike about Git?** There is a bit of a learning curve, and it can be even harder to learn if you are used to svn, which uses a completely different workflow. but those are minor gripes. **Recommendations to others considering Git:** Do it, don't hesitate, just dive in. Github has a ton of free workshops to help you learn git, Stack overflow is rife with experienced git users (including myself) who are ready and will to help with any problems. it might feel big and hard, but it isn't. just start using it, you will find it makes you and your team more efficient. **What problems is Git solving and how is that benefiting you?** concurrent work, ease of merging, not being dependent on the network. basically every gripe about svn, is solved with git. ### 42. Great distributed control system for your code base **Rating:** 4.5/5.0 stars **Reviewed by:** Carmelo C. | Software Development Engineer, Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** May 15, 2015 **What do you like best about Git?** Mature and advanced revision control system which allows multiple distributes teams to work to different features using a single code base with minimal interruptions. Good supporting tools, online documentation and active community. It has a great flexibility to satisfy almost all needs in a development environment, and it supports multiple OS. **What do you dislike about Git?** Coming from a TFS background, first think I noticed was missing is the ability to force gated check-ins (or at least we didn't find a way of doing it). Moreover, integration with IDEs like Visual Studio and Eclipse might sometimes be painful. To get full benefits of it, command line usage is a must, but not all people like it. Moreover, it's not easy to find code review tools which offer a proper review iterations management that integrate into GIT **Recommendations to others considering Git:** At the begin there are a few steps to digest before becoming fully productive, especially if you come from a different control system. Use blogs and official documentation to learn GIT and find out more about it since it's really powerful and offer many advanced features. Better getting used to Git Bash rather than Git UI since the first one is more powerful and offers more controls. Use GitExtensions to visualize graphically different branches and their status. Finally, not related to GIT but always a good practice, use good comments when making check-ins **What problems is Git solving and how is that benefiting you?** Supporting development of multiple features using a single codebase. Great for branching and merging code. ### 43. Slow ramp up; Huge upside **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.) **Reviewed Date:** July 28, 2015 **What do you like best about Git?** I like git once I started to retain and understand the madness that is Git. In terms code versioning, it is the best on the planet. You never really lose code unless you lose your repo. **What do you dislike about Git?** The ramp-up. It takes a while just to learn how to use its "happy path". Once you've conquered that, you have to learn how to dig yourself out of typically scenarios: conflicts, codebase out of sync, rolling back commits - the pitfall list is immense. **Recommendations to others considering Git:** There are great tutorials for Git out there on the interwebs: The Happy-path Guide: http://rogerdudler.github.io/git-guide/ The "Oh, you've done it now" Guide: http://sethrobertson.github.io/GitFixUm/fixup.html#pushed **What problems is Git solving and how is that benefiting you?** We write software in the business banking industry. With so many chefs in the kitchen it is important to look at history of a file and go back to that commit hash and pull content that may missing in future iterations bc someone over-wrote your changes. Unless something destroys your repo (local or remote), you never really lose code. i would call it somewhat bulletproof. Not idiot proof. ### 44. Best in class **Rating:** 5.0/5.0 stars **Reviewed by:** Peter B. | Hands-on Engineering Manager, Mid-Market (51-1000 emp.) **Reviewed Date:** May 12, 2015 **What do you like best about Git?** Git is severely awesome. It makes source control a joy rather than a chore. I use git on everything because it is so lightweight and easy to initialize for any kind of file. Changing a binary-only LEGO MINDSTORMS project with your LEGO League team? Put it in git, branch it, be able to travel in time and between different kids' work with ease. **What do you dislike about Git?** People who haven't used git - I feel terrible for them! Can you imagine a world where source control is a hassle, or worse, where changes are (gasp!) lost? Git is such a valuable tool, I truly mourn for those who aren't using it. I've used a number of other source control tools (clearcase, svn, accurev, perforce) and they just pale in comparison to the usefulness and power of git. **Recommendations to others considering Git:** Learn it and become expert in its use - well worth the investment. It can seem like a steep learning curve coming from other tools, but dive in and you'll benefit a great deal. **What problems is Git solving and how is that benefiting you?** I'm using git on a number of projects, work and personal, and admin'ing it. Benefits are seamless travel up and down branches, great visibility into when changes are introduced, and a super sharp, powerful tool that we can script around and benefit from. ### 45. Still learning git ... **Rating:** 4.5/5.0 stars **Reviewed by:** Tonya E. | Software Engineer, Small-Business (50 or fewer emp.) **Reviewed Date:** July 22, 2015 **What do you like best about Git?** Git is SOO powerful. I am a previous SVN user, so being able to have multiple local branches and push to the trunk is wonderful! I also like the ability to be able to stash changes, until I am ready to commit. Git is light weight, yet a very powerful version control system. **What do you dislike about Git?** There really isn't much that I dislike, except for the fact that it takes a while to be a git power user. Anyone using git in their daily workflow should take the time to master the basic commands. I love git (coming from being a SVN user). **Recommendations to others considering Git:** Learning git is a somewhat steep learning curve. It is best to depend on someone that you know to help you figure out all of the nuances. There is almost, always a way to revert or fix a change (and multiple ways to accomplish the same task)-- but you still need to be very carful. The git website has useful documentation, but again, you need to take the time to practice and learn. Once you get it, you will fall in love with git too! **What problems is Git solving and how is that benefiting you?** Multiple developers working not he same code base. Need to have version control and review changes being committed. ### 46. Git will change the way you work **Rating:** 5.0/5.0 stars **Reviewed by:** Kevin K. | Principal Software Engineer, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** July 21, 2015 **What do you like best about Git?** Most all SCMs allow you to branch and merge, but what drew me to git was the ability to stash a set of changes without needing to commit them. Often times you find yourself in the middle of fixing one issue when a critical issue comes in and trumps your current work. Git stash allows you to move those changes off to the side so you can work from a clean branch. Once your critical issue is committed, you can restore your stashed changes and be on your way. Git also allows you to commit specific hunks (or lines) of a file. There are times you want to break your changes up to several commits that may cross files. **What do you dislike about Git?** Coming from a centralized VCS like CVS or SVN, there is a bit of a steep learning curve in understanding how git works. You also have to get used to the fact that it doesn't use sequential revision numbers for each commit. Instead, each commit has a unique sha1-hash. **Recommendations to others considering Git:** It will change your life. **What problems is Git solving and how is that benefiting you?** Git helped make the development more efficient and improved our code review and release process. ### 47. Git and CI implemented auto publish for websites **Rating:** 5.0/5.0 stars **Reviewed by:** Frank M. | Product Architect, Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** May 04, 2015 **What do you like best about Git?** Git is extensible and flexible. It works with modern development practices in mind. We can use different branches for different versions of sites and merge code into each of them from development and feature branches. Conflict resolution is much better than in SVN or CVS **What do you dislike about Git?** There is no real receive only version of a git repo so end place publishing has to be shell scripted pulls. When pushing from an automated source like Jenkins and using the git push methodology, there are fast forward issues. That makes this system of publishing very difficult. A --receiveonly flag on git repo init that would create a repo that is designed to only take git push commands from a central CI or git server would be very helpful. **Recommendations to others considering Git:** when creating a git repo you have the option for --bare. I would like to see one called --live or --receiveonly so that we can always push to it without all the head issues that come with a deployment. This would stop us from having to ssh to the server and issue a git pull in the shell. **What problems is Git solving and how is that benefiting you?** I am currently implementing architecture of a Continuous Integration and Unit Tested workflow stream for a health care start up that is centered on Git and Jenkins. ### 48. Easily the new standard for version control **Rating:** 4.5/5.0 stars **Reviewed by:** James R. | Software Engineer, Internet, Enterprise (> 1000 emp.) **Reviewed Date:** December 17, 2015 **What do you like best about Git?** Git is very fast and makes it very easy to recover from mistakes. You pretty much have to try to delete history in order to make that happen. **What do you dislike about Git?** I've heard from other friends that Git doesn't scale well - other than that I can't complain. **What problems is Git solving and how is that benefiting you?** Version control is a problem that could be managed in a lot of different ways, but Git seems to have the necessities and then some for the more advanced learner. ### 49. Very good and used by many, version control tool **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Banking | Mid-Market (51-1000 emp.) **Reviewed Date:** December 09, 2015 **What do you like best about Git?** Being able to sync my repositories and share my projects. **What do you dislike about Git?** Not being able to store some of my projects privately without having to pay a fee. **Recommendations to others considering Git:** Git is one of the best version control tools, in my opinion. Bit bucket is also a good tool and can be better than Git if you are using JIRA to manage your projects. **What problems is Git solving and how is that benefiting you?** It is my main version control tool for my dev projects. ### 50. One of the best revision control systems **Rating:** 5.0/5.0 stars **Reviewed by:** Michal M. | Principal Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** July 28, 2015 **What do you like best about Git?** Git allows our teams to work in a non-linear development environment and retain high efficiency across the board. Git comes with a great and strong branching support, which consumes the minimum space necessary provides more options you can think of. **What do you dislike about Git?** If there is one thing to name, it's git's weak support for binary files. Each binary file is stored separately and there is no (binary)diff to help with it. And there is always one coworker who commits that 13MB package :/ **Recommendations to others considering Git:** git is free. Go ahead and download it. Play with it. Don't forget to check out "git blame" , which perfectly aligns with Torvald's personality (which you may love and hate at the same time) **What problems is Git solving and how is that benefiting you?** Our daily use consists of version controlled automation base as well as code development. Tagging really helps with our release management. ## Git Discussions - [What is Git used for?](https://www.g2.com/discussions/what-is-git-used-for) - 4 comments, 1 upvote - [sdfsfdsfsfdsfsfsfsfsfsfsfsf](https://www.g2.com/discussions/sdfsfdsfsfdsfsfsfsfsfsfsfsf) - 2 comments, 1 upvote - [what is the most channeling use of Git in your experience](https://www.g2.com/discussions/29849-what-is-the-most-channeling-use-of-git-in-your-experience) - 2 comments - [View Git pricing details and edition comparison](https://www.g2.com/products/git/reviews?page=10§ion=pricing&secure%5Bexpires_at%5D=2026-05-25+15%3A32%3A40+-0500&secure%5Bsession_id%5D=a0dab840-1404-4cd5-b981-fd767b5ca880&secure%5Btoken%5D=1506e2991e28d16411de93ca89c761f24e8a5c57bae53222e1f7fc7fef2db51f&format=llm_user) ## Git Integrations - [Android Studio](https://www.g2.com/products/android-studio/reviews) - [Azure Pipelines](https://www.g2.com/products/azure-pipelines/reviews) - [Bitbucket](https://www.g2.com/products/bitbucket/reviews) - [CoPilot AI](https://www.g2.com/products/copilot-ai/reviews) - [Cursor](https://www.g2.com/products/cursor/reviews) - [Cypress](https://www.g2.com/products/cypress/reviews) - [Docker](https://www.g2.com/products/docker-inc-docker/reviews) - [Eclipse](https://www.g2.com/products/eclipse/reviews) - [Git](https://www.g2.com/products/git/reviews) - [GitHub](https://www.g2.com/products/github/reviews) - [GitHub Copilot](https://www.g2.com/products/github-copilot/reviews) - [GitHub Inc.](https://www.g2.com/products/github-inc/reviews) - [Github Package Registry](https://www.g2.com/products/github-package-registry/reviews) - [GitKraken Desktop](https://www.g2.com/products/axosoft-gitkraken-desktop/reviews) - [GitLab](https://www.g2.com/products/gitlab/reviews) - [GitLens](https://www.g2.com/products/gitlens/reviews) - [IBM Terraform (formerly HashiCorp Terraform)](https://www.g2.com/products/ibm-terraform-formerly-hashicorp-terraform/reviews) - [IntelliJ IDEA](https://www.g2.com/products/intellij-idea/reviews) - [Jenkins](https://www.g2.com/products/jenkins/reviews) - [Jira](https://www.g2.com/products/jira/reviews) - [Kubernetes](https://www.g2.com/products/kubernetes/reviews) - [MuleSoft Anypoint Platform](https://www.g2.com/products/mulesoft-anypoint-platform/reviews) - [Nimble CRM](https://www.g2.com/products/nimble/reviews) - [PyCharm](https://www.g2.com/products/pycharm/reviews) - [Selenium WebDriver](https://www.g2.com/products/selenium-webdriver/reviews) - [Slack](https://www.g2.com/products/slack/reviews) - [Slack Connector for Jira](https://www.g2.com/products/slack-connector-for-jira/reviews) - [SlackNotify](https://www.g2.com/products/slacknotify/reviews) - [SONAR](https://www.g2.com/products/sonar-2025-01-07/reviews) - [SourceTree](https://www.g2.com/products/sourcetree/reviews) - [Visual Studio Code](https://www.g2.com/products/visual-studio-code/reviews) - [Xcode](https://www.g2.com/products/xcode/reviews) ## Top Git Alternatives - [Azure DevOps Server](https://www.g2.com/products/azure-devops-server/reviews) - 4.2/5.0 (192 reviews) - [P4](https://www.g2.com/products/p4/reviews) - 4.2/5.0 (93 reviews) - [AWS CodeCommit](https://www.g2.com/products/aws-codecommit/reviews) - 4.2/5.0 (81 reviews)