Change a workspace ID

Changing your workspace ID will change the URL for all associated repositories, snippets, and any static websites you're hosting on Bitbucket Cloud.

A workspace is how you organize different streams of work in an account. You can change your workspace ID in Bitbucket Cloud; however, this will change the URLs for all the repositories, snippets, and static websites you're hosting on Bitbucket Cloud.

Change your workspace ID for repository, snippet, wiki, and website URLs

Changing your URL is a two-part process. You first update the workspace ID in Bitbucket Cloud and then in your configuration file.

Update the workspace ID in Bitbucket Cloud

  1. From your profile avatar, select the workspace you want to update or All workspaces for a list of all your workspaces.

  2. Select the Settings cog on the top navigation bar.

  3. Select Workspace settings from the Settings dropdown menu.

  4. Select (change) to the right of your workspace ID.

  5. Enter your new workspace ID. Your workspace ID can only contain lowercase letters with no spaces or special characters.

  6. View the repositories that will be impacted to confirm you understand the impact of this change.

  7. Follow the prompts to confirm the change.

  8. Update any configuration files, builds, or references to the old URLs.

This change on the remote on-prem server invalidates any local repositories pointing to your repositories on Bitbucket. You and anyone who references the old URL in DVCS configuration files must update them to reflect the new workspace ID. 

For example, if you rename your workspace ID from johnc to jcitizen, the repository previously available at http://bitbucket.org/johnc/repo is accessed as http://bitbucket.org/jcitizen/repo after renaming.

Update the URL in your configuration file

The URL you use for a repository depends on which protocol you're using: HTTPS or SSH. You can find these URLs from the Clone button on the Source page of your repository.

You can move back and forth between the SSH and the HTTPS protocol links to see how the URLs differ. The table below shows how the formats vary based on protocol.

You'll see these names as part of the URL:

  • In place of <repo_name>, you'll see the repository name.

  • In place of <workspace_ID> in the HTTPS URL format, you'll see the workspace ID for your workspace.

Git repository URLs

HTTPS format

https://<your_username>@bitbucket.org/<workspace_ID>/<repo_name>.git

SSH format

git@bitbucket.org:<workspace_ID>/<repo_name>.git

or

ssh://git@bitbucket.org/<workspace_ID>/<repo_name>.git

Update the URL for Git repositories

  1. From a terminal, navigate to the repository.

    $ cd ~/<path_to_repo>

  2. Run git remote -v to see the current remote URL.

    $ git remote -v
    origin https://emmap1@bitbucket.org/tutorials/tutorials.git.bitbucket.org.git (fetch)
    origin https://emmap1@bitbucket.org/tutorials/tutorials.git.bitbucket.org.git (push)

  3. Update the remote URL with git remote set-url using the current and new remote URLs.

    $ git remote set-url origin git@bitbucket.org:tutorials/tutorials.git.bitbucket.org.git

If you update your URL from HTTPS to SSH, the next time you push or pull from your repository, the terminal responds that it is adding the Bitbucket host to the list of known hosts. You also won't have to enter a password.

Still need help?

The Atlassian Community is here for you.