https://github.com/cyotek/svngitmigrate
Simple tool to aid in doing partial migrations of an SVN repository to Git
https://github.com/cyotek/svngitmigrate
csharp git svn svn2git
Last synced: 7 months ago
JSON representation
Simple tool to aid in doing partial migrations of an SVN repository to Git
- Host: GitHub
- URL: https://github.com/cyotek/svngitmigrate
- Owner: cyotek
- License: mit
- Created: 2020-12-21T21:37:19.000Z (almost 5 years ago)
- Default Branch: master
- Last Pushed: 2024-12-27T16:31:57.000Z (11 months ago)
- Last Synced: 2025-03-24T03:43:54.641Z (8 months ago)
- Topics: csharp, git, svn, svn2git
- Language: C#
- Homepage:
- Size: 552 KB
- Stars: 6
- Watchers: 1
- Forks: 3
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE.txt
Awesome Lists containing this project
README
# Cyotek Svn2Git Migration Utility
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
## How does it work?
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.
## Selecting Revisions
![Selecting revisions][step1]
* 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
## Mapping Authors
![Entering author mappings][step2]
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 `.
## Inclusions and Exclusions
![Defining exclusions][step3]
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.
## Selecting the Git Repository
![Selecting the Git Repository][step4]
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.
## Preview
![Generating an optional preview][step5]
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.
## Migrate
![Selecting the Git Repository][step6]
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.
[step1]: res/step1.png
[step2]: res/step2.png
[step3]: res/step3.png
[step4]: res/step4.png
[step5]: res/step5.png
[step6]: res/step6.png