Forking repositories under same project

[Fifi Chau]

Hi, we are migrating from Bitbucket DC to Bitbucket cloud and I found that the forking behavior is a bit different from what we are currently doing in DC. 

When forking in cloud, it appears that we need to choose workspace and project as well, which would have two outcomes: 

1. All forked repos would fall into the project, which is what we don't want to see;

2. Developers need to create their own project to save those forked repos, however they would need to be granted as workspace admin to create project, which also does not make sense to us. 

May I know if any better ideas? Thanks a lot.

[Theodora Boudale]

Hi Fifi,

Every repository in Bitbucket Cloud needs to belong to a workspace and a project within that workspace.

You could create a separate project only for forks within your workspace and grant developers Create access to that project. The developers will then be able to create their forks in that project.

When a developer creates a fork in that project, they will have admin access to the fork they create, and write access to other repositories (not created by them) in that project.

Would that work for you?

Kind regards,
Theodora