Move repo to another existing project (Bitbucket Cloud)

Wanderley Teixeira

In Bitbucket Cloud, I want to move repoA that is in projectA to projectB.

I see that I can go to repoA settings and there's a drop down list of project that I can select. After I save, what are the side effects of this move (if any)? 

It seems that the clone url is the same, and all it does it literally move repoA and all its settings (permissions, etc) to projectB after I click to save the project change. Am I missing anything here?

Daniil Penkin

Hello @Wanderley Teixeira,

Thanks for reaching out.

You're right, clone URL and repository URL don't change when you move that repository between projects. In fact, you can think of projects as of single-value labels: they're used to group repositories but don't introduce any hierarchy in terms of configuration. The only exception to this is that private project can only contain private repositories. That said, you won't be able to move a public repository into a private project, and you won't be able to make a private repository public while it belongs to a private project. Public project can contain both public and private repositories, so this is not inheritance but rather some constraint for repositories in private projects.

All other permissions and settings are per repository, and project adds nothing on top of that.

Hope this helps. Let me know if you have any questions.

Cheers,
Daniil