Update: There have been reports of hanging on the import authors page and the import itself. The bug has been fixed, if you were having trouble, please try your import again.
Importing a subversion repository into git, while not overly difficult, can definitely be streamlined, especially when your goal is to host it on GitHub.
There is now a link on the ‘Next Steps’ page after you’ve created your repository that’ll let you import your hosted subversion repository.
All you need is your svn repo’s url and we’ll take care of the rest.
Check out the screencast below to watch the magic happen (turn up your speakers). Enjoy!
Assuming that this retains history… how does this handle matching svn usernames to github users? For some of our projects, we did this manually and had to build a svn authors file to map things.
curious
Very nice. Any support for cloning private repositories planned?
Very cool. Does it persist the git-svn connection so that you can do `git svn fetch` into a branch, in order to merge new commits to the svn repository into git repo?
@robby the importer asks you to associate the usernames before it imports
@rictic no, it’s our gentle way of saying it’s time to move to git full-time :-)
Very nice! Great feature. Too bad there is no rebase feature!
Thanks.
I think the fan sound in the background is from the GitHub cluster as it gears up to process the Subversion import.
Boo to no automated rebasing. This would be delicious for cloning projects managed by other ppl in svn repos automatically.
Is there anyway to tell if this has hung or not?
I imported something around 8 hours ago and it’s still at it :/ It was only a 40meg repo or so, too.
I second drninc. it’s not my project so i can’t tell everyone to move (though I did ask politely if they’d thought of it), but i’d much rather follow it through git than svn, and it seems silly to have lots of people tracking their own copies when github could provide a central one for git lovers. Then if enough commits are made to the git version first it would become clear what most devs preferred, and would be easier for the project to move on from svn.
Are there any plans to do this? I would like to track Magento development through git instead of svn.
+1 for maintaining svn synch. It would make svn import a powerful force for bringing more high-profile projects into git, especially all those crunchy open source projects on Google Code with lots of (svn-weary) committers!
Does this work 100%? I have tried to import a project from google code a number of times and the closet I have gotten in using this import except the trunk was not imported into the master like I expected. I have 5-8 tags and 1 additional branch in svn and am using standard layout. However everything imported just fine, except the all important trunk. Any thoughts?
It doesn't bring in svn externals... not good!