Focus on code.
Develop code as a team. Keep all your development in one place, be it issue tracking, documentation or sharing code.
It all just got easy.
Bitbucket.org is a premium platform for doing just that. See why over 56400 users already signed up, and be more productive, today.
Bitbucket: silky smooth version control sprinkled with awesome mercurial flavored toppings.
— Mischa Leuffen
Find code & projects
E.g. "django-", "tortoise" or "mercurial"
Have a closer look
So what is Bitbucket?
Bitbucket is a code hosting site, for the popular Mercurial version control system. With Mercurial, your data is distributed by definition, but you still need a place to share it, and keep track of your development.
Bitbucket is that. It provides a fully featured environment for managing development, including a wiki (naturally backed by Mercurial, you can clone it!), a powerful issue tracker, and easy collaboration with others.
Simply put, it takes the pain out of sharing code, and lets you focus on what you do best: Code.
What do I get?
|
HTTP push/pull support |
|
|
SSH push/pull support (with public key authentication) |
|
|
Integrated flexible issue tracker |
|
|
Per-repository wikis (backed by hg repositories) |
|
|
Plenty of "services" for repositories, automatic issue resolving, web hooks, etc. |
|
|
Email support (for both paid and free plans) |
|
|
CNAME support, so you can keep the code on your own domain |
|
|
Collaborate with other users easily |
|
|
Source view with highlighting for many languages |
|
|
Forks and Mercurial Queue (MQ) integration |
|
|
A bunch of social aspects |
|
|
RSS/Atom feeds for everything |
|
|
Host static files on our CDN (Content Delivery Network) |
What's Mercurial then?
Mercurial is a distributed version control system, or DVCS for short. It is in the ranks of Git and Bazaar, leading a new paradigm of working with version control.
If you have been using other version control systems like CVS or SVN, you should feel right at home, as Mercurial's command set is very similar.
The main difference between a traditional version control system and a distributed one is that the distributed system does not rely on one central server. Every person with a repository also has the full history of changes. Each repository is independent.
In Subversion, for example, each developer checks out a copy from the main server, works on changes, and commits them back in. In case of conflicting changes made by other developers, you will be notified and asked to merge the changes. In a DVCS world, this is different, as commits are local, and you can commit several dozens of changes locally without ever communicating with anyone else.
Join the ranks of..
