SVN to Git Migration

Approach & Aims

Make use of an already existing guide
Retain a complete history of the code
No need to go back to the SVN repo
Keep svn as a "just in case" back up

Challenges

Developers to move to Git without disruption
Ability to sync SVN to Git during above process
Retain a comprehesive code history

LIVE DEMO

Lessons Learned

1. Research GIT!

Take the time to read up about GIT. Try some commands out.

or risk diving straight in like I did!

2. Connection drops

Run on a server

3. git svn clone

Be careful of a complicated SVN Repo
More branches = More time to run
Excluding a branch can cause havoc

4. Only migrating the trunk

No GIT branches
No record of deleted files

5. Persevere

Git may feel like this at first

But it wont take long to feel like this

Any questions?

Here's a guide!