When you create a Bitbucket Cloudrepository, you specify whether it's private or public, but you can also change this setting at any time.
If your repository is public, anyone can access and fork it.
If your repository is private, you can specify who exactly can access your repository and whether they can fork it.
You can set your Bitbucket repository, wiki, and issue tracker as private or public, independently of each other. For example, you can hide your code from the world by setting your repository as private, but let people see your documentation and issues by marking your wiki and issue tracker as public. Or you could set your repository and wiki as public but keep your issue tracker private. For more details, see Make the tracker private or public and Make a wiki private or public.
Set repository privacy status
A private repository is visible only to users who have permission to see it. A public repository is visible to everyone.
From the repository, click Repository settings in the sidebar.
LocateAccess levelon theRepository detailspage. Add or remove the checkmark fromThis is a private repositorybased on your preferred privacy status.
Click Save repository details.
Set forking permissions
Forking permissions allow you to specify whether and how a user can fork your repository. Because public repositories allow public forks, you must make your repository private to restrict forking.
From the repository, clickRepository settingsin the sidebar.
From theRepository detailspage, if you don't see theForkingoption, selectThis is a private repository.
From theForkingdropdown, select one of the following options:
Allow forks—Users can fork the repository and those forks can be public.
Allow only private forks—Users can fork the repository and those forks will be private.
No forks—Users can't fork the repository.
ClickSave repository details.
