Managing and versioning source code and assets

Source code should be versioned so that changes to your code can be undone, should you run into unforeseen issues. We should also have clear visibility on who did what, when, how, and why. With classic SharePoint solutions, such as full-trust code projects, the versioning system was typically Microsoft's Team Foundation Server (TFS), an on-premises service that could be deployed locally. It would provide a portal for accessing different team projects, managing tasks, bugs, project schedule, and resources. TFS is still widely used, but it's fairly complex to deploy and configure, and numerous version upgrades in past years have proven that such services can also be provisioned as cloud-based services.

For the SharePoint Framework-style projects, you should typically choose either GitHub.com (a third-party cloud service), which allows you to store your project data and code in a private or public repository, or Visual Studio Team Services (VSTS), which is a service from Microsoft and hosted through the Microsoft Azure public cloud offering. GitHub is hugely popular, as basic use is free, and it's widely accepted as a trusted party for hosting your code. As you saw before, all Office Dev PnP repositories are hosted on GitHub. Enterprise developers might be inclined to choose VSTS, TFS, or a similar platform for source control, as that might be the platform their IT department supports and maintains.