GitHub ends Subversion support in January 2024
GitHub’s Git Systems team has announced that Subversion (SVN) support will be retired on GitHub.com on January 8, 2024. A GitHub Enterprise Server release scheduled for early 2024 will also drop SVN functionality.
Subversion support dates back to 2010, when centralized version control systems were still the norm and Git was regarded as the newcomer. GitHub’s SVN compatibility layer let teams keep working in SVN while the underlying repository ran on Git, easing the transition to a distributed version-control workflow.
That migration story no longer matches reality. Git now counts as many as 94% of developers among its users, and Subversion traffic on GitHub has dropped accordingly. Fewer than 0.02% of requests to GitHub’s Git backend arrive via a Subversion endpoint, and just around 5,000 repositories receive even a single SVN request per month.
The engineering trade-off has also shifted. Even a feature with little traffic still carries ongoing maintenance and security obligations for an internet-facing service. With Subversion usage that low, the team has decided to direct those efforts entirely at Git.
When customers and communities were asked why they still relied on SVN, the main answer was partial checkout workflows: fetching only a subdirectory or only the latest commit. Modern Git addresses those use cases with sparse checkout, the sparse index, and partial clone, which can effectively pull down just the portion of a repository that a developer needs.
Subversion support is still fully functional until January 8, 2024. Late in 2023, GitHub will run brownout periods lasting a few hours and then a full day to surface any remaining dependencies on the feature. After the cutoff date of January 8, the service will be disabled and removed, and the first GitHub Enterprise Server release shipped after that day will exclude SVN support as well.
