GitHub Sunsetting Subversion Support
github.blog
GitHub Sunsetting Subversion Support
1–10 of 238 posts
Re: GitHub Sunsetting Subversion Support
#2About time... I don't know a single person that still uses it. I can't tell you how many times I got burned doing merges in Subversion where the entire repo became corrupt. Git was a life saver when it came out and I switched immediately over to it.
Re: GitHub Sunsetting Subversion Support
#3About time... I don't know a single person that still uses it. I can't tell you how many times I got burned doing merges in Subversion where the entire repo became corrupt. Git was a life saver when it came out and I switched immediately over to it.
> I can't tell you how many times I got burned doing merges in Subversion where the entire repo became corrupt.
Earlier in my career, in the first week at one company I ended up corrupting the Subversion repo. I was a nervous wreck. My boss reassured and told me about he had also corrupted a Subversion repo previously as he restored the repo from backup.
Re: GitHub Sunsetting Subversion Support
#4Not sure I’m familiar with any projects using Subversion. I think the most odd-ball version control I’ve seen in prod is SQLite using Fossil (which does seem to have benefits over git) and OpenBSD sticking with CVS.
Re: GitHub Sunsetting Subversion Support
#5No!
Re: GitHub Sunsetting Subversion Support
#6Not sure I’m familiar with any projects using Subversion. I think the most odd-ball version control I’ve seen in prod is SQLite using Fossil (which does seem to have benefits over git) and OpenBSD sticking with CVS.
SVN is a relatively sane option, especially before git was published. But in 2023 its mostly been replaced.
Re: GitHub Sunsetting Subversion Support
#7About time... I don't know a single person that still uses it. I can't tell you how many times I got burned doing merges in Subversion where the entire repo became corrupt. Git was a life saver when it came out and I switched immediately over to it.
> I can't tell you how many times I got burned doing merges in Subversion where the entire repo became corrupt. Earlier in my career, in the first week at one company I ended up corrupting the Subversion repo. I was a nervous wreck. My boss reassured and told me about he had also corrupted a Subversion repo previously as he restored the repo from backup.
Uggh. If there's one thing I would want to be super stable it would be my version control!
Re: GitHub Sunsetting Subversion Support
#8[deleted]
Re: GitHub Sunsetting Subversion Support
#9Didn't even know GitHub had svn support... it's been about a decade since I've even had to interact with a subversion repo professionally also.
Re: GitHub Sunsetting Subversion Support
#10There is only one thing about subversion I miss when using git -- the deletion of branches (which were, admittedly, just directories in a folder called branches) was version controlled, so you could recover deleted branches.