base on A Scalable, User-Friendly Source Control System. # 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](https://sapling-scm.com/docs/introduction/getting-started) page for how to clone your existing Git repositories. Checkout the [Overview](https://sapling-scm.com/docs/overview/intro) for a peek at the various features. Coming from Git? Checkout the [Git Cheat Sheet](http://sapling-scm.com/docs/introduction/git-cheat-sheet). Sapling also comes with an [Interactive Smartlog (ISL)](http://sapling-scm.com/docs/addons/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 `sl` command 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](https://www.mercurial-scm.org/), and shares various aspects of the UI and features of Mercurial. The CLI code can be found in the `eden/scm` subdirectory. ### Mononoke [Mononoke](eden/mononoke/README.md) 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. ### EdenFS EdenFS is a virtual file system for managing Sapling checkouts. 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. EdenFS speeds up operations in large repositories by only populating working directory files on demand, as they are accessed. This makes operations like `checkout` much faster, in exchange for a small performance hit when first accessing new files. This is quite beneficial in large repositories where developers often only work with a small subset of the repository at a time. More detailed EdenFS design documentation can be found at [eden/fs/docs/Overview.md](eden/fs/docs/Overview.md). ## Building the Sapling CLI The Sapling CLI currently builds and runs on Linux, Mac, and Windows. It can be built by running `make oss` in the `eden/scm` directory and running the resulting `sl` executable. Building the Sapling CLI requires Python 3.8, Rust, CMake, and OpenSSL for the main cli, and Node and Yarn for the ISL web UI. ## Getting in Contact You can [Report an Issue on GitHub](https://github.com/facebook/sapling/issues) or [Join the Discord](https://discord.gg/X6baZ94Vzh) # License The main project is licensed under [GPL-2.0](LICENSE). The [website](website) and [ISL](addons) are licensed under [MIT](addons/LICENSE). Library subprojects, such as [minibytes](eden/scm/lib/minibytes), might have different licenses. Please refer to the `LICENSE` file and source code headers in each library for detailed information. ", Assign "at most 3 tags" to the expected json: {"id":"1907","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"