Summary On January 8, 2024, we will turn off Subversion support in GitHub.com. We will also turn off Subversion support in the first GitHub Enterprise Server release after January 8, 2024. Intended…
Summary On January 8, 2024, we will turn off Subversion support in GitHub.com. We will also turn off Subversion support in the first GitHub Enterprise Server release after January 8, 2024. Intended…
TIL It had svn support 😮
Makes sense though. It enabled them to siphon off existing SVN codebases from — whatever the hell they were doing previously — and facilitate their transfer to git.
First turned on in 2010.
Git-svn was always the blessed path for converting. GitHub supporting svn was more about getting heterogeneous orgs to buy enterprise subscriptions.
I thought Github only supported git, too. Did it support Mercury at some point? I assume this is the last of other VCS support in Github.
Mercurial* and no, GitHub never supported hg, that was kind of the distinguishing feature of bitbucket back in the glory days of VCS plurality.
Now if you need mercurial hosting, heptapod (a friendly fork of gitlab with mercurial support) is a great way to go
I was half-asleep when I wrote this, lol. Bitbucket dropped Mercurial recently, too. Sourcehut is the only other code forge I know of that supports hg which I really love. Kind of sets a high bar for contributions, but not being vendor locked in is a bonus. And I wish they’d more tightly integrate the subdomains…