What it does
Mercurial is a distributed source-control management tool. Each clone contains project history, so developers can review and commit work locally without a central server being reachable. Its quick start covers cloning a project, adding files, committing a change, and pushing it to a shared repository.
A quick start uses hg clone to create a local copy, hg add for new files, and hg commit to record a change. When the team is ready to share, hg push transfers the committed work to a remote repository. A new project can instead begin with hg init. Mercurial's distributed history suits teams that want each working copy to carry the project's revisions. Repository hosting is a separate service, and teams already using another VCS need to agree on one system for a shared project rather than mix histories casually. Mercurial's official site identifies its source as GPLv2 or later.
Strengths
- A clone includes the project's revision history, allowing local work without constant network access.
- The official quick start documents both cloning an existing project and initializing a new one.
- The project is available under the GNU GPL version 2 or later.
Watch out for
- A team still needs a compatible remote repository or hosting workflow to share changes.
- Teams already standardized on another version-control system need a deliberate migration or interoperability plan.
Best for
- Teams that want distributed history and local commits for versioned project files.
- Developers learning source control through a short clone, add, commit, and push workflow.
Sources
- About | Mercurial SCM (Oct 25, 2026)
- Quick Start | Mercurial SCM (Oct 25, 2026)
- Mercurial (stable branch): COPYING (Oct 25, 2026)