Hello Atlassian Team,
We are in middle of a org demerger and restructuring. We would like to clone our existing BitBucket cloud repos from existing workspace to new workspace.
Migrate option doesn't work us, because source organization doesn't want to loose the repo access. We are only allowed to clone repos to new workspace.
We also gone through this existing support ticket - https://community.atlassian.com/t5/Bitbucket-questions/I-have-the-requirement-of-copying-the-bitbucket-project-from/qaq-p/1781148. git checkout --mirror and git push --mirror would work but we will loose the pull request history
Is there a way to clone along with pull request history?
In our case, it the same team that is going to use the new repo, our bit_bucket accounts also retained with same username, so it we could carry forward pull request history that would help the continuity
Any suggestion would be highly appreciated
Thanks in advance
Bala
Hi Bala,
Welcome to the Bitbucket Cloud community!
Regarding your concern about pull requests not showing up in a repository that has been cloned and pushed to a new workspace, this behavior is expected. Pull requests are treated as metadata generated by Bitbucket Cloud, allowing collaborators to review changes quickly. They do not exist as part of Git itself. Consequently, cloning and pushing a repository does not carry over pull request history.
The only way to migrate pull request history to the new workspace is to transfer the repositories, although I understand that the source organization wants to maintain repository access.
Once the repositories have been transfered to the new workspace, you can grant them access. This way, they maintain access, and the pull request history is preserved.
I hope this information helpful.
Cheers,
Phil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.