I'm currently interning and I've been tasked with migrating our enterprise repositories from Azure DevOps (ADO) to GitHub (GH). I'm running into some challenges specifically with transferring the pull requests (PRs). Has anyone dealt with this before or have any tips on how to navigate the process?
5 Answers
Another option is to back up your ADO environment and restore it in GitHub. Tools like GitProtect allow you to use their backup & DR solution to do this effectively. While it's primarily for data protection, it does facilitate data migration with a cross-restore option from ADO to GitHub.
PRs and comments don't transfer neatly during migration, so keep that in mind.
By the way, what’s the main reason for migrating? ADO isn’t going away anytime soon.
One approach is to write code to recreate the PRs and their comments since there's no straightforward migration path for that. Personally, I think it's best to close all open PRs, migrate the main branch, and start fresh. If you face pushback from the team about any long-lived branches, that's a good indicator that a reset could be beneficial and you might want to shift towards trunk-based development.
That's a great question! I think a major reason is all the cool plugins available for GitHub, like Copilot. Some claim ADO has support for similar tools, but many find those versions to be buggy and not as well-tested.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically