Comment 3 for bug 1846887

Hope things are going well! I've been poking at this in my free time and have mad a lot of changes to the migration script I posted before and wanted to provide an update.

I mostly focused on testing the migration but the refactors came with some "Features"
- Its better at pulling incremental changes so you don't need to rebuild everything all the time(pulling all the bzr branches and even the git import take a while)
- I can migrate and test specific branches in isolation now
- A test script now that does some comparisons from bzr and git

One failed changes, originally I tried comparing the entire history of the branches. It turns out that even though git can format the individual commits so they are _very_ close to bzr's format, git organizes its history slightly different and this doesn't seem feasible. By this I mean in the flat linear view of commits, commits from merges seem to "appear" in a different order even when logically everything is the same. The code is still in the repo if anyone wants to take a look but I couldn't get output that seemed useful to me.

The test script does compare the source code after the migration and this seems to work great. Attached are the diffs between the git and bzr branches after the migration. Key takeaways:
- The maddump branch didn't work. :( I didn't see any errors but I'll keep looking at this.
- PY8meetsMG5aMC has one directory containing a link that shouldn't be there. ¯\_(ツ)_/¯
- Every other branch is identical!
- Its not in the diffs because I suppressed it but there are a lot of empty directories in some bzr branches and git can't store empty directories. Where it makes sense I would suggest adding a .gitkeep or .gitignore file to hold the directories after the migration. This is the standard solution when an empty directory is needed as a placeholder or to document a structure.