This repository hosts a naive utility for creating a Git repository from an existing SVN folder, making it useful for breaking a mono SVN Repository into smaller Git repositories.
This tool is a work in progress that I did for breaking up my own repository. It may not work for all cases, for example if root folders were renamed or moved.
It has only received limited testing and is provided AS-IS
In the simplest fashion possible - you give it a location in SVN, it will enumerate the revisions in that location and will check each one out in reverse order and check them into a Git repository with the appropriate date, author and log information. That is it, nothing fancy.
The code is a little messy, I did start to break it up into more reusable and testable components but this work is ongoing.
- Enter the URL of the remote SVN path you want to migrate. This will then list all revisions associated with that location
- Select the revisions you wish to migrate
SVN uses a simple name for attribution, but Git requires a name
and email address pair. The Author Mapping tab will list any
detected authors for the selected revisions, for each author
ensure there is a name and email address in the pattern
svn_name = git_name <git_email>.
If there are files you want to exclude from the new repository (for example a scratch program full of credentials that should never have been committed to begin with!), you can configure a set of include or exclude patterns to manage which files will be copied from each SVN checkout to the Git repository.
Enter glob patterns in either the inclusion or exclusion fields, or both. Files will only be included if they are both included and not excluded. If the includes field is blank, then all files are included. If the excludes field is blank, then no files will be excluded.
For example, if you had a folder named /src/Scratch in your
repository which you didn't want migrated, then you could enter
the glob /**/Scratch to the exclusion list.
Don't use backslashes in globs, the migration tool will automatically handle conversion from Windows paths.
Enter the local folder where the Git repository will be located.
If you are creating a new repository, ensure the folder is empty the Use existing repository option is unchecked.
If you want to append the commits to an existing repository, ensure the folder points to the existing repository and check the Use existing repository option. This can be useful if you are having to build a Git repository from multiple sources, e.g. if a root folder was renamed or moved.
Click the Preview button to display a simplified preview. This will scan the revisions and test changed files against inclusion and exclusion patterns, then print a list of all matched files. This can be very useful to make sure you have your patterns set right, and also to review file lists in case you see something that needs adding to the exclusions.
Note that this isn't bullet proof, for example in my testing it didn't show a large number of files from an initial migration into SVN from SourceSafe.
Click the Migrate button to start the process. For each selected revision, this tool will check that out, sync the contents with the Git repository (honoring include/exclude rules), then perform a commit.