You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
All of our developers work in forks of our shared repositories. The only way changes are made to our shared repositories is via pull requests.
When testing the BitBucket Cloud Migration tool we noticed that along with forks not being migrated, our entire pull request history is lost despite the many thousands of them showing in the summary counts of what will be migrated.
This is a complete show stopper for our migration. If this is not possible then we may as well migrate to a different platform.
How do we migrate our forks and preserve our pull request history?
I'm assuming this is for a server to cloud migration. If so, the Bitbucket Cloud Migration Assistant is the only method of migrating repos while preserving pull request history. Please take a look at this link for further information https://www.atlassian.com/migration/resources/bitbucket-migration-assistant
Hi Dexter, from the page https://support.atlassian.com/migration/docs/plan-your-bitbucket-server-to-cloud-migration/ we can see that "... we do not support migrating forked repositories. Merge any open pull requests from forks to prevent any data corruption prior to migrating to the Cloud."
What's strange is that for merged pull-requests on most of our repositories the pull-requests and the comments and tasks do come across, albeit with some broken links.
For one repository, our main one, no pull requests come across and the migration assistant reports an error. Attempting to download the migrationErrorReport file gives a HTTP 404 error so we have no idea what the actual problem is.
I acknowledge BitBucket's deficiencies with forked repositories but this is frustrating as we can't diagnose what's going wrong in the migration of our main repository when it's working for our other ones.