Configure repository settings

A private repository is visible for users with permission while a public repository is visible to everyone.

Grant access (admin, read, or write) to people who will need to review or work on code with you in a repository.

Access keys allow you to force authentication when pulling or cloning a repository.

Map existing non-mapped email aliases to user accounts from the username aliases page.

Set up a link between Bitbucket Cloud and any external service.

Change or transfer the ownership of a repository to another team or to an individual.

We recommend repositories be kept under 2.0 GB to ensure that our servers are fast and downloads are quick for our users.

Learn how to remove unwanted files from a Git repo.

Deleting a repository permanently removes it from Bitbucket Cloud.

All Bitbucket Cloud repositories come with the ability to create branches and pull requests.

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.

Configure branch permissions to enforce specific workflows and prevent errors.

Merge checks allow you to recommend or require specific conditions on merges for individual branches or branch patterns.

The pull request view shows each file modified in the pull request.

To change the remote URL for a repository, you'll need to update the configuration file with the new URL.

Use webhooks to integrate applications with Bitbucket Cloud.

Understand how webhooks work in Bitbucket Cloud.

If you aren't sure if a webhook triggered properly, you can look at the details of the request.

Let's create a webhook and see if we can trigger it