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."We have developed automation to speed up common repetitive processes."
"Apache Subversion is a scalable solution."
"The features that I have found most valuable are that it can support you for most of the road map and it can automate some tasks which works really well with collaboration with the teams. They are really interested in how they organize the history of the code itself which is good."
"GitHub is good for collaboration because everyone can access it or we can restrict access to a few users. If I upload a file and share the URL, it's not restricted to a set number of users. Everyone with the link can download the files."
"The version control functionality for this solution has been most valuable, especially when managing projects with multiple versions."
"GitHub have a built-in software application development environment and this has been most useful."
"Even if I'm not in the office, I can access and work on my code from anywhere with my account credentials."
"The most valuable feature is the fact that it's cloud-based, and we don't have to manage an on-premises server to use it."
"It has a lot of features from the code development perspective. You get a lot of features such as repo, commit, merge, and branch. You can play around and do things on the fly. It is easy and simple to deploy. It is also easier to use when working from home."
"I find GitHub very user friendly."
"Apache Subversion should be easier to use."
"The most valuable feature is CLI."
"Lacks sufficient support in terms of professional services that could be provided."
"The ticketing system is not working."
"GitHub could have better integration or capability with other solutions."
"The development team pushes the code into a repository, and the CI/CD pipeline will perform the build. We need open-source libraries to perform the builds. It would be helpful to have the ability to link to open-source libraries like npm libraries. I don't know if GitHub Actions provides this. I would like to see that in GitHub Actions if they don't."
"The GitHub repository needs an upgraded user interface and overall UI improvements."
"I would like to see integration with Slack such that all of the changes made in GitHub are reflected there."
"The initial setup and implementation could be easier, I had some difficulties with it at first but I don't have a development background."
"While using the solution when merging two code branches the code becomes a bit messy. This should be improved in the future."
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.
