To see what can be cleaned up, run the following command in ~/GitMigration/ : java -Dfile.encoding=utf-8 -jar ~/svn-migration-scripts.jar clean-git This is an advanced task, as is not recommended for the typical project. However, if you’re planning on committing to the Git repository and the SVN repository during the migration process, you should not perform the following commands. If you’re following this migration guide, this isn’t a problem, as it advocates a one-way sync from SVN to Git (the Git repository is considered read-only until after the Migrate step). Note that this is a destructive operation, and you will not be able to move commits from the Git repository back into the SVN repository. The clean-git script included in svn-migration-scripts.jar turns the SVN branches into local Git branches and the SVN tags into full-fledged Git tags. That’s why our next step will be to convert these remote branches to local branches and actual Git tags. This behavior makes certain two-way synchronization procedures easier, but it can be very confusing when trying to make a one-way migration Git.

The git svn clone command imports your SVN branches as remote branches and imports your SVN tags as remote branches prefixed with tags/. But, if you run git branch -r, you’ll find all of the branches and tags from your SVN repository. You won’t find any of your SVN branches in the git branch output, nor will you find any of your SVN tags in the git tag output. You should be able to switch into ＜git-repo-name＞ and run any of the standard Git commands to explore your project.īranches and tags are not imported into the new Git repository as you might expect.

Git svn clone -trunk=/trunk -branches=/branches -branches=/bugfixes -tags=/tags -authors-file=authors.txt / Inspect the new Git repositoryĪfter git svn clone has finished (this might take a while), you’ll find a new directory called ＜git-repo-name＞ in ~/GitMigration. Run the following command in the ~/GitMigration directory: If your SVN project uses the standard /trunk, /branches, and /tags directory layout, you can use the -stdlayout option instead of manually specifying the repository’s structure. Depending on the structure of your SVN repo, the command needs to be configured differently. The git svn clone command transforms the trunk, branches, and tags in your SVN repository into a new Git repository. This will avoid the overhead of cloning via a network connection.

However, if you have a very large SVN repository and want to cut down on the conversion time, you can run git svn clone on the SVN server instead of on the migration lead’s local machine. As a benchmark, converting a 400MB repository with 33,000 commits on main took around 12 hours to complete.įor reasonably sized repositories, the following steps should be run on the migration lead’s local computer. We’ll do this with the git svn utility that is included with most Git distributions, then we’ll clean up the results with svn-migration-scripts.jar.īeware that the conversion process can take a significant amount of time for larger repositories, even when cloning from a local SVN repository. The next step in the migration from SVN to Git is to import the contents of the SVN repository into a new Git repository.

Smartgit svn