, a successful commercial git hosting provider that hosts over a million repositories, offers reliable free open source git hosting service now, I decided to go ahead and move the source code that I had in last 8 years from sourceforge subversion repository to GitHub. This page documents the steps that I did, which was pretty simple and smooth anyway.
- Obviously I need to be a user in GitHub.com. It's easy to sign up, no confirmation is required.
- Create new repository from here, and import from a public subversion URL. The URL is something like http://<projectname>.svn.sourceforge.net/svnroot/<projectname>.
- Before import starts, you are required to tell more about each user discovered from subversion repository. The user name and email address each sourceforge user maps to doesn't have to be existing user in GitHub.com.
- It takes very very long time for import to finish. Be patient.
- I already have git on my computer. If you don't, find out how it's installed on your operating system. If you don't know what git is, stop here and start spending some time on http://git-scm.com.
- Tell GitHub.com the public SSH keys of each computer that wants to work with the git repository. Sourceforge does it too. Goto Account Settings/SSH Public Keys and update the keys.
- Assume the import is done. Before pulling code to local, a little configuration is required. This document describes several properties to set. The properties are to tell GitHub.com who the user is. They end up stored in <USERHOME>/.gitconfig file.
- Find a working directory, run the git clone command to get local copies.
git clone firstname.lastname@example.org:<user>/<repository name>.git
Post a Comment