We performed a comparison between Git and GitHub based on real PeerSpot user reviews.
Find out in this report how the two Version Control solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The tool's most valuable feature is branch workflows."
"Git is easy to use."
"The most valuable feature of Git is the ease of tracking in time what the snapshot of the code was at a particular moment. The versioning is good."
"I use the solution for website management."
"I like that it's easy to use and because it's accessible from a terminal or a graphical user interface if needed. I also like that we can pass comments from Linux if required."
"Git is a product everyone uses, so it's almost inescapable. I like the fact that there is a large ecosystem around it. You can bolt various graphical user interfaces onto it or sign up for various repositories like GitHub and AWS CodeCommit. Git has a large community, so there are lots of resources and knowledge bases you can use."
"We use the tool to store codes."
"I believe it is beneficial to maintain a detailed log or history of who did what to a project and which user committed to the change."
"I did not have any issues with the stability of Github. It worked seamlessly."
"We are finding GitHub is very stable."
"This product is very good for storing and versioning code."
"The solution has been stable for us."
"It's beneficial for managing multiple tasks and controlling versions of your product."
"Any complex banking can be handled very easily in GitHub. It allows us to integrate with tools like Grid, where we can merge and resolve conflicts without any hassle."
"The product has a good UI. It's simple and easy to access, and technical help is easily available. The two-factor authentication security is another valuable feature."
"The ease of use is valuable."
"The tool is complicated for a beginner. You need to have some training to use it. It is also hard to find a parameter."
"The price could be improved."
"Some challenges arise when Git is not used correctly, particularly in managing branches. It's easy to get lost, but these challenges can be overcome with proper management. A common advice is maintaining the repository and ensuring developers are in sync with the production branch. Branches should be promptly merged into development to avoid getting lost in many branches."
"New developers sometimes find it difficult to call a review or create a request."
"It's not very user-friendly."
"If other people are included in their project, you're going to have to make merge requests to merge the code you made, and the code your colleagues have made. So it's a little bit complicated."
"The scalability could be better. I think it requires some discipline to have large teams working on the same project without facing problems merging code. I'm using Git for personal projects, but I know companies face merge conflicts when more than one person is working on code simultaneously."
"Git removed the credential feature."
"It would be better if the amount of storage were increased."
"GitHub should provide more integration in their next release, including integrating with Jenkins, CI/CD and Jira."
"The solution should have less integration with the AI part, but it needs to add features with other automation tools so that it can be easily integrated."
"This solution could be improved if migration was fully automated to make it easy, for example, to migrate repositories into GitHub."
"If it had all of the end-to-end integration, then we probably wouldn't have any doubts about what we have installed. However, at this point, we're still trying to figure out how to use it end-to-end."
"We want to incorporate management comments within GitHub, making it more like a product management tool. We haven't done that yet. Another change we're considering is migrating from GitHub to Azure DevOps, especially now that Microsoft has introduced it."
"The UI is a little outdated, so that could be improved."
"They're improving the work items to track the progress of the team, but in my experience, Azure DevOps is better in this functionality. GitHub needs to improve the form to track the progress of the work done by a team."
Git is ranked 4th in Version Control with 37 reviews while GitHub is ranked 3rd in Version Control with 74 reviews. Git is rated 8.6, while GitHub is rated 8.6. The top reviewer of Git writes "A stable solution that can aid its users in maintaining all application developments ". On the other hand, the top reviewer of GitHub writes "Beneficial version control and continuous integration, but guides would be helpful". Git is most compared with Atlassian SourceTree, Canonical Bazaar, Surround SCM, IBM Rational ClearCase and Helix Core, whereas GitHub is most compared with Snyk, AWS CodeCommit, Fortify on Demand, Bitbucket and Atlassian SourceTree. See our Git vs. GitHub report.
See our list of best Version Control vendors.
We monitor all Version Control reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
