Git proxy 2.0 migration guide

[kriswest]

Is your feature request related to a problem? Please describe.
Git Proxy 1.* adopters may need to handle some breaking changes in order to migrate to 2.* when released

Describe the solution you'd like
Write a Git Prooxy 1.* -> 2.* migration guide that includes:

• Details of breaking changes and new features
• Changes needed to migrate (notably includes repo URLs needing to end in .git, updated proxy urls (containing the SCM provider URL and changes to the config schema)
• Troubleshooting guide

[jescalada]

@kriswest I'm working on going through the migration process to document errors and their solutions. Will get a draft of this for you to expand on if there's anything missing!

[kriswest]

Awesome thanks @jescalada.

I think one of the main challenge is making sure repo URLs end in .git (or they don't work anymore). I'm not sure that 100% correct (i.e. I'm not sure that it's required.in the got protocol, but its useful and all the SCM providers we've seen do it.

We either need to document that or add a migration of some sort. I don't like the idea of doing it on every start-up TBH, but I wonder if it's time we added some form of migration setup...