I am admin on a public bitbucket repository, which I'd like to configure to only allow private forks that by default are readable by the development team of the original repo.
Is there a a way to achieve this?
Sofar I have actually been unable to configure my public repo to allow only private forks - the option to modify forking behavior only appears in the admin panel when the repo itself is marked private.Is this by design or is there a glitch in the bitbucket UI here?
No, this is by design. If you are working with a public repository, then it is assumed that the forks are public as well. If you are working in private, then you can enfore privacy permissions on forks. However, we recommend using the same repository with Branch restrictions to ensure your entire team is working from the same code.
If you'd like to see the behavior changed, you can log a request to https://bitbucket.org/site/master/issues/new.</span<>>
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 ...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot