If you’re looking for a better experience to manage your Git repositories, this guide introduces you to using Git with Visual Studio Code.

Git’s command line has, for lack of a better way of describing it, evolved into somewhat of a conflicting journey. In learning how to use source control, you will inevitably begin using Git. Not only does source control protect you and your team from mistakes, but it also forces you into a habit of standard project organization practices. VSCodium exists to make it easier to get the latest version of MIT-licensed VS Code.In previous articles, we’ve tried to make it clear that source control is non-negotiable to becoming a software engineer even if you work alone as an independent developer or contractor.

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.

Visual studio repository