We performed a comparison between Apache Subversion 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."Apache Subversion is a scalable solution."
"We have developed automation to speed up common repetitive processes."
"I use this solution to store my code in a repository so we can manage version control which is useful."
"I find GitHub very user friendly."
"The most valuable feature of GitHub is version control and continuous integration."
"The best feature is the ability to track the history of all code changes, and it's easy to use. Additionally, as it's open source, anyone can use that feature resulting in distributed development. This opens the door to collaboration with different code and developer, feature, and master branches of development."
"During our use of GitHub, we have not encountered any problems and GitHub adds new features frequently."
"Complication free with good ability for third-party integrations."
"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."
"We use GitHub instead of our regular shared drive. It offers instant access to shared folders as well as good security."
"Apache Subversion should be easier to use."
"The most valuable feature is CLI."
"If you are uploading or cloning a large file, with more than 25 megs, it's pretty slow."
"GitHub storage is one of the main requirements and it could improve."
"GitHub could improve by being more user-friendly."
"There can be conflict issues when two developers work on the same file or line of code, and it would be great to see that improved, possibly with an AI solution."
"GitHub needs to improve its UI."
"I would like to see more security where a plugin was available for us to update in relation to security."
"The solution can improve by adding video guides, official guides, or short courses that cater to beginners who are new to the system. These resources could offer step-by-step guidance on how to use GitHub, including common procedures such as pulling and committing. Currently, many of us have to resort to searching for information on how to do these tasks via Google. An official guide provided by GitHub itself would be a valuable asset to newcomers and would save them time and effort."
"GitHub's issue management could be improved a little from an organization standpoint. It would be helpful to have the ability to organize a work board or a backlog more comprehensively. For organizations migrating to GitHub from arbitrary systems, it's a little bit of a headache to move on to that system."
Apache Subversion is ranked 9th in Version Control with 4 reviews while GitHub is ranked 3rd in Version Control with 64 reviews. Apache Subversion is rated 7.2, while GitHub is rated 8.6. The top reviewer of Apache Subversion writes "Centralized repository, but the stability could improve". On the other hand, the top reviewer of GitHub writes "Beneficial version control and continuous integration, but guides would be helpful". Apache Subversion is most compared with IBM Rational ClearCase, whereas GitHub is most compared with Snyk, AWS CodeCommit, Atlassian SourceTree, Bitbucket and Fortify on Demand. See our Apache Subversion 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.
