Skip to content

Bitbucket

Bitbucket Cloud stores shared Git repositories and gives teammates a place to review changes before they are combined.

Visit Bitbucket

Where does your code go when you send it to Bitbucket?

Bitbucket Cloud puts a repository in an Atlassian workspace. Keep a local Git copy and send only the commits you intend to share. This profile covers Cloud. Atlassian’s self-managed Data Center product has separate plans and operation.

Confirm the workspace and repository visibility before sending a branch. Check which groups have repository access. Choose the team’s workspace if the team needs to keep the project when one person leaves.

Will a missing approval stop a merge?

A pull request shows changes and lets people review them. Bitbucket Cloud offers branch restrictions and can recommend checks before a merge. The documented setting that prevents a merge with unresolved checks is a Premium feature.

Check both who can merge and whether the branch requires the result you expect. A review warning can still leave the merge available. Avoid assuming a check is required just because it appears next to the change.

What counts toward the plan and what can you back up?

Atlassian lists Free for up to five workspace users with unlimited public and private repositories. Build minutes and large-file storage have separate allowances. Check the billing screen for the paid options that apply to your organization.

A mirror copy can preserve the Git history. If your project uses Git LFS, which stores large files separately from their references, verify that the actual files can be opened from the backup. A repository copy does not carry the site’s pull request discussions or issues.

How can you tell a suggestion from a required check?

Draw a fictional pull request for a checkout button label. Keep all accounts and real repositories untouched.

  1. Mark who may merge
    Draw a reviewer and the person allowed to combine the changes. Give the reviewer one thing to check about the new wording.
  2. Rehearse an unresolved review
    Draw the request with no approval. Under recommended checks, mark the warning. Under an enforced required check, mark that the merge should wait.
  3. Write the recovery list
    Mark the last working commit, any large file and the review discussion as separate items. Decide how you would verify each one was preserved.