Enhancing GitHub Migrations with Additional Tooling | josh-ops

[utterances-bot]

Enhancing GitHub Migrations with Additional Tooling | josh-ops

A collection of additional tools to assist with your GitHub migration experience

https://josh-ops.com/posts/github-migration-tools/

[R3V0LTAWAK3NING]

Super helpful article, and has informed a lot of my own migration planning. One question that I have - if you're going from one GitHub Enterprise to another and choose to rename the original organization and apply that name to the new one, would users still need to clone the repositories again from the new org? My assumption is that since the org slug isn't changing their remotes would still be in tact and should be able to work seamlessly as long as they're using an SSH key paired with their new account (we're going from GHEC to EMU in our case).

[joshjohanning]

Thank you for the feedback @R3V0LTAWAK3NING 😄

One question that I have - if you're going from one GitHub Enterprise to another and choose to rename the original organization and apply that name to the new one, would users still need to clone the repositories again from the new org?

Good question! In my prior tests, users will NOT have to change their local remotes since the URL is ultimately staying the same for them and nothing is otherwise changing with the Git repos themselves.