When you create a repository there are certain settings that need to be configured, such as granting access to other users, assigning the repository to a workspace, and setting your version control system.
For more information about particular repository settings, check out the topics here.
Set repository privacy and forking options
A private repository is visible for users with permission while a public repository is visible to everyone.
Grant repository access to users and groups
Grant access (admin, read, or write) to people who will need to review or work on code with you in a repository.
Add access keys
Access keys allow you to force authentication when pulling or cloning a repository.
Map existing commits to username aliases
Map existing non-mapped email aliases to user accounts from the username aliases page.
Link to a web service
Set up a link between Bitbucket Cloud and any external service.
Transfer repository ownership
Change or transfer the ownership of a repository to another team or to an individual.
Reduce repository size
We recommend repositories be kept under 1.0 GB to ensure that our servers are fast and downloads are quick for our users.
Maintain a Git repository
Learn how to remove unwanted files from a Git repo.
Maintain a Mercurial repository
Learn how to reduce repository size by removing large files from a Mercurial repo.
Delete a repository
Deleting a repository permanently removes it from Bitbucket Cloud.
Pull request and merge settings
All Bitbucket Cloud repositories come with the ability to create branches and pull requests.
Git fast forwards and branch management
Learn the situations when Git will do a fast forward when you merge a branch that is ahead of the branch you have checked out.
Use branch permissions
Configure branch permissions to enforce specific workflows and prevent errors.
Suggest or require checks before a merge
Merge checks allow you to recommend or require specific conditions on merges for individual branches or branch patterns.
Exclude files from pull request diffs
The pull request view shows each file modified in the pull request.
Change the remote URL to your repository
To change the remote URL for a repository, you'll need to update the configuration file with the new URL.
Manage webhooks
Use webhooks to integrate applications with Bitbucket Cloud.
Event payloads
Understand how webhooks work in Bitbucket Cloud.
Troubleshoot webhooks
If you aren't sure if a webhook triggered properly, you can look at the details of the request.
Create and trigger a webhook tutorial
Let's create a webhook and see if we can trigger it
Was this helpful?
