Sapling SCM
Sapling SCM is a cross-platform, highly scalable, Git-compatible source control system.
It aims to provide both user-friendly and powerful interfaces for users, as well as extreme scalability to deal with repositories containing many millions of files and many millions of commits.
Using Sapling
To start using Sapling, see the Getting Started page for how to clone your existing Git repositories. Checkout the Overview for a peek at the various features. Coming from Git? Checkout the Git Cheat Sheet.
Sapling also comes with an Interactive Smartlog (ISL) web UI for seeing and interacting with your repository, as well as a VS Code integrated Interactive Smartlog.
The Sapling Ecosystem
Sapling SCM is comprised of three main components:
- The Sapling client: The client-side
slcommand line and web interface for users to interact with Sapling SCM. - Mononoke: A highly scalable distributed source control server. Not yet supported publicly, OSS is buildable for unsupported experimentation.
- EdenFS: A virtual filesystem for efficiently checking out large repositories. Not yet supported publicly, OSS is buildable for unsupported experimentation.
Sapling SCM's scalability goals are to ensure that all source control operations scale with the number of files in use by a developer, and not with the size of the repository itself. This enables fast, performant developer experiences even in massive repositories with millions of files and extremely long commit histories.
Sapling CLI
The Sapling CLI, sl, was originally based on
Mercurial, and shares various aspects of the UI
and features of Mercurial.
The CLI code can be found in the eden/scm subdirectory.
Mononoke
Mononoke is the server-side component of Sapling SCM.
While it is used in production within Meta it is not yet supported for external usage. OSS builds in GitHub Actions are available for unsupported experimentation.