If you have already configured a credential helper and Git identity, you can skip to the next task.įrom the main menu, select Terminal | New Terminal to open a terminal window.Įxecute the command below to configure a credential helper. In this task, you will configure a Git credential helper to securely store the Git credentials used to communicate with Azure DevOps.

This lab requires you to complete task 1 from the prerequisite instructions (Skip cloning, it is done in the exercise).Įxercise 1: Configuring the lab environment Visual Studio Code with the C# extension installed. You will use Visual Studio Code, but the same processes apply for using any Git-compatible client with Azure DevOps. In addition, you will learn about Git branching and merging support. In this lab, you will learn how to establish a local Git repository, which can easily be synchronized with a centralized Git repository in Azure DevOps. You should use Git for version control in your projects unless you have a specific need for centralized version control features in TFVC. Git is the default version control provider for new projects. Developers can commit each set of changes on their dev machine and perform version control operations such as history and compare without a network connection. Each developer has a copy of the source repository on their dev machine. Git repositories can live locally (such as on a developer’s machine). Git: Git is a distributed version control system. Branches are path-based and created on the server.

Historical data is maintained only on the server. Typically, team members have only one version of each file on their dev machines. Team Foundation Version Control (TFVC): TFVC is a centralized version control system. Here is a quick overview of the two version control systems: Azure DevOps supports two types of version control, Git and Team Foundation Version Control (TFVC).

Visual studio code git disappears mac