Skip to main content

bitbucket-sync synchronize locally all the repositories of a bitbucket account

Project description

Synchronise all git repositories of a bitbucket account to local git clones.

Synchronising means, remote repositories are cloned to local disk and later updated by changes in remote repository. This tool never pushes updates from local disk to remote server.


by pip from pypi:

$ pip install bitbucket-sync

by pip from github:

$ pip install git+

Get credentials to access bitbucket account

To access repositories under your bitbucket account, you need to configure the account for that and get required OAuth tokens called Key and Secret.

  1. go to - (your lovely avatar) - Manage account - Integrated applications

  2. In section “OAuth consumers” click “Add consumer” and a form appears

  3. Fill in some information (it is not really important what it will be):

    Name: bitbucket-sync

    Description: Synchronise all git repositories of a bitbucket account to local git clones.


    and click “Add consumer”.

  4. You will be presented with a page showing Key and Secret strings. These strings will be used in following calls to bitbucket-sync.

Note, that the Key and Secret will become accessible in the same place (OAuth consumers) in Bitbucket, where you created it. There is no need to recreate it again.

Synchronizing your repos from bitbucket to local directory

Initially clone all git repos you own on bitbucket

Having a bitbucket account, e.g. “Gautier”, bitbucket will show a set of git repositories prefixed with this account name “Gautier/”. These are the repos, owned by that account.

To clone all bitbucket git repos owned by given user account to local disk:

$ mkdir archive
$ cd archive
$ bitbucket-sync --key xxxxOAuthKeyxxx --secret yyyyOAuthSecretyyy --directory . --owner Gautier

This creates a subdirectory named Gautier with one deeper subdirectory per cloned repository.

Fetch all updates from bitbucket repos owned by given account

The process is very simple, just repeat the call as before:

$ bitbucket-sync --key xxxxOAuthKeyxxx --secret yyyyOAuthSecretyyy --directory . --owner Gautier

All updates on bitbucket will be fetched down to local repositories.

All new repositories will be cloned.

There is no process of cleaning repositories which were removed from bitbucket.

Repositories renamed on bitbucket will be considered new ones (and cloned).

Syncing other repositories, you have direct access to

If other users incl. team accounts grant you access to repositories owned by them, you will get a chance to sync them too.

Syncing repos from explicitly named owner

You just change owner in the call and you get it done:

$ bitbucket-sync --key xxxxOAuthKeyxxx --secret yyyyOAuthSecretyyy --directory . --owner vlcinsky

Syncing all repos accessible by your account

If you omit the –owner parameter, all repositories you have access to will be synced:

$ bitbucket-sync --key xxxxOAuthKeyxxx --secret yyyyOAuthSecretyyy --directory .

As usually, there will be one subdirectory per owner, and then all related repositories in it.

Questions and Answers

Does the tool synchronizes Mercurial repositories?

Yes, as long as mercurial is installed locally.

Does it clone all publicly accessible repositories from bitbucket?

Simply no.

The tool takes into account only repositories:

  • created (and owned) by you
  • created by someone else and with explicit grant of permission on that repository for your account.

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Filename, size & hash SHA256 hash help File type Python version Upload date
bitbucket-sync-0.3.1.tar.gz (4.2 kB) Copy SHA256 hash SHA256 Source None

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN SignalFx SignalFx Supporter DigiCert DigiCert EV certificate StatusPage StatusPage Status page