In bitbucket cloud, how can private fork be accessible to teamates ?

Hugo Gerard

We use a classic fork & pull request workflow, that we used on bitbucket server:

• a teamate forks the main repository 
• he works on an issue in a branch 
• he then create a pull request for it to merge it to the main repository.

Our main repository is private, and forks are also private.

When a reviewer review a teamate work, he sometimes needs to access his private repository. But if the teamate give access to the whole team, we get "You’ll need to upgrade your plan before adding more users." (while we have already an upgraded plan for the team). 

Are we missing something ? How do we implement this workflow ?

Thanks

 

Ana Retamal

Hi Hugo! The reviewers won't be able to access a private fork unless they're granted access to it, in which case they'll need to use a license. If you already have 5 people with access to that repo, you'll need to upgrade your plan.

If the repo is owned by an individual account (not by the team account), this account's plan will restrain the number of people that can access it. So if the individual account is on the Free plan and is trying to grant access to a team that contains more than 5 members, this will not work because the Free account allows 5 users at max. 

Instead of giving access to the whole team, you could try granting access only to the specific reviewer and remove him later when he doesn't need access anymore, to avoid reaching the Free plan limit.

I hope this info is clear, Hugo! Please let us know if you have any questions and we'll be happy to help.

Have a nice day,

Ana