Fork in a Private Repo

Hi,

The company who I work for, build a Private Repo, to manage the source code of the main software.

My question is: The company has 4 developers, all signed in bitbucket; and the company want to open fork in this private repo. But they had one question: After the developer make the fork, after while the company fire him, and delete the user in private project, in other words.. cancel the access of this user in the project. What's happen with fork? the user still work in the code?

Regards,

4 answers

1 accepted

0 vote
Jason Worley Atlassian Team Nov 12, 2013

The fork is in a separate silo from the original repository. If you make changes on a fork, your changes only impact your fork. When you push the changes, they push to your fork. When you make a pull request Bitbucket bundles up your changes from your fork and sends them as a pending request on the original repository. When the owner of the original repository accepts the request, then your changes are seen on the original repository.

This will not affect other people's work; unless you want it to. For example, you may choose to work with another person on your fork.

That being said, the user will have the code, that is generally a benifit of the DVCS model. You obviously would want to immediately restrict the user from having access to the repository.

Please reference the following info for more details:

https://confluence.atlassian.com/display/BITBUCKET/Manage+groups

This is not really a group setting issue.

This is a genuine concern for company using the service.

If a repository is private. There should be an option for the repo owner to have access to all the forks from that repo.

If someone leaves the project or company, the company should be able to regain control of the fork and delete it.

Is there somewhere to submit a feature request for this?
This is a question waiting to come up in a compliance audit.

Our work around is to required all developers to assign the owner of their forks back to the company account. For these repo, set to "no fork" allowed.

Not a nice solution but it answer the question if there is a compliance audit.

This is a genuine concern for company using the service.

If a repository is private. There should be an option for the repo owner to have access to all the forks from that repo.

If someone leaves the project or company, the company should be able to regain control of the fork and delete it.

Is there somewhere to submit a feature request for this?
This is a question waiting to come up in a compliance audit.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

1,950 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you