However, cloning repos takes time and maintenance, as your local copy can quickly become out of date if you don't pull changes regularly. We may want to look at the source code of a library we use, experiment with new tools, or just feel the desire to learn something new. Why do you need GitHub Repositories?Īs developers, we often clone Git repos locally just to browse them or make small edits. The GitHub Repositories extension lets you quickly browse, search, edit, and commit to any remote GitHub repository directly from within Visual Studio Code. VSCodium exists to make it easier to get the latest version of MIT-licensed VS Code.This is the pre-release edition of GitHub Repositories for early feedback and testing. If you want to build from source yourself, head over to Microsoft’s vscode repo and follow their instructions. These binaries are licensed under the MIT license. This project includes special build scripts that clone Microsoft’s vscode repo, run the build commands, and upload the resulting binaries for you to GitHub releases. The VSCodium project exists so that you don’t have to download+build from source. Therefore, you generate a “clean” build, without the Microsoft customizations, which is by default licensed under the MIT license When you clone and build from the vscode repo, none of these endpoints are configured in the default product.json. We clone the vscode repository, we lay down a customized product.json that has Microsoft specific functionality (telemetry, gallery, logo, etc.), and then produce a build that we release under our license. When we build Visual Studio Code, we do exactly this.
According to this comment from a Visual Studio Code maintainer: Microsoft’s vscode source code is open source (MIT-licensed), but the product available for download (Visual Studio Code) is licensed under this not-FLOSS license and contains telemetry/tracking.
0 kommentar(er)
