Share your code with Visual Studio 2013 and Azure Repos Git

Azure Repos | Azure DevOps Server 2019 | TFS 2018 | TFS 2017 | TFS 2015

Whether your software project is large, small, or brand new, in most cases you'll be better off if you use version control as early as possible. Here, we'll show you how to get started with Git, a distributed system. If you want to work in a centralized system, you can instead use TFVC with Azure Repos.

Open your project in Visual Studio

  1. Before you start, if you haven't already:

  2. Go to your project's page ({yourorganization}/{yourteamproject}) and then open Visual Studio to connect to your project.

    On your project overview page, click Open in Visual Studio

  3. Sign in to Azure DevOps Services from Visual Studio.

Clone your repository

  1. Clone the repository onto your dev machine.

    Choose Clone Repository

  2. Store the repository locally.

    Choose Clone to store the repository locally

Create a new app

If you don't already have an app in the repo, create one.

  1. Create a new project.

    New solution from team explorer

  2. Choose a template and add the new code project to version control.

    Choose a template

Confirm your settings and add the app

  1. On the changes page (Keyboard: Ctrl + 0, G), if you haven't already done it, confirm your user name and email address.

    Configure settings from the changes page

    Confirm the default settings

  2. Add a comment and commit your app to version control.

    Add app to version control on Changes page

Snapshot (commit) your code

With your code project stored in a local Git repository on your dev machine, you can commit as early and as often as you like.

  1. As you write your code, your changes are automatically tracked by Visual Studio. You can commit one or more specific changes to your local repository from Solution Explorer (Keyboard: Ctrl + Alt + L).

    When your changes are ready, select Commit

  2. On the Changes page, add a comment and then commit your changes.

    Add a comment and choose Commit

    These changes are now committed.

    Your changes are now committed

Pull changes from your team

Pull changes on a regular basis to ensure your code integrates well with the latest code from the team.

  1. From the commits page (Keyboard: Ctrl + 0, O), fetch the commits to see any changes that your team has made.

    Choose Fetch to see any changes that your team has made

  2. When you're ready, pull these commits into your local repository.

    Choose Pull to get these commits locally

  3. The changes from your team are now integrated in your local repository.

    The changes are now integrated

Push your local commits to the server

When the code you've written on your dev machine is ready, you can push your changes from your local Git repository to the project.

  1. From the changes page (Keyboard: Ctrl + 0, G), make sure you've committed your changes.

    Committing from the Changes page

  2. Go to the commits page (Keyboard: Ctrl + 0, C).

    Push changes

  3. Push your changes.

    Push changes


Q: Why is my sign-in page different than when I sign in to Visual Studio?

A: Your sign-in page depends on whether you used a Microsoft account or work account with Azure DevOps Services. So, sign in with the username and password that you used with Azure DevOps Services.

Q: Why doesn't Visual Studio launch when I click "Open in Visual Studio" on my project page?

A: This link requires Visual Studio 2013 or later. It doesn't launch earlier versions of Visual Studio.

Q: How can I see what I've changed?

A: To see what you've changed, compare your changes with the last commit.

Choose Compare with Unmodified from the context menu

Q: How can I get more information about the commits from my team before I pull them?

A: Sometimes you need to see the details about incoming commits from your team. That way you can understand how a change will integrate with your work.

Choose View Commit Details

You can get details on the changes to each file.

Choose Compare with Previous from the context menu

A: From the changes page you can run a query, and then drag a work item into the list of related work items.

Associating a work item on the Changes page

Q: Can I use Git command-prompt tools?

A: Yes. See Use Git from the command prompt.

Q: Where can I learn more?

A: Use Visual Studio and Team Foundation Server with Git