Run this command on behalf of the same user you use to serve Git repository:
$ subgit configure --layout auto --trunk trunk SVN_URL GIT_REPO |
where
SVN_URL
– the URL to the SVN project.
GIT_REPO
– the path to the new Git repository where data from the SVN project will be imported to.TRUNK
– the path, relative to SVN_URL
, leading to the SVN directory that acts as the main line of development.
|
Specify authors mapping
Configure authors mapping in default authors mapping file:
GIT_REPOS/subgit/authors.txt |
Or change core.authors
option so that it points to the global authors mapping file.
Find more details about authors mapping in the Authors mapping article.
Import data into local Git repository by the command:
$ subgit import GIT_REPO |
where
GIT_REPO
– the path to the Git repository.
|
step into the newly created local Git repository
$ cd GIT_REPO |
add a remote to the local Git repository:
$ git remote add github GITHUB_REPO |
where
GITHUB_REPO
– GitHub project URL.push local repository content into GitHub repository:
|
When the command completed, the local repository is not needed anymore and can be removed:
$ rm -Rf GIT_REPO |
All the files from SVN are now on GitHub, so you can clone your GitHub repository and start to work with it:
$ git clone GITHUB_REPO WORK_TREE |
where
WORK_TREE
– the path to your working copy.GITHUB_REPO
– GitHub project URL
|
If Git warns you that you are cloning an empty repository and you don't see your files in the working tree, most probably automatic branches and tags mapping didn't work correctly. In this case, mapping has to be set manually, see details on mapping in Branches and tags mapping. |
For one-time import, no license is needed. |
Should you need any assistance, don't hesitate to contact us at support@subgit.com.