Share your code with Azure Repos and Visual Studio

Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019

Visual Studio 2019 | Visual Studio 2022

Share your Visual Studio solution with others by hosting your code in an Azure Repos Git repository. You can use Visual Studio to manage Azure Repos Git repositories or GitHub repositories. This article provides procedures for the following tasks:

• Add a project or solution to a local Git repository
• Publish your code to an Azure Repos Git repository or GitHub repository
• Review your code changes before publishing
• Link work items to your commits
• Commit and push updates
• Pull changes from the main branch of your repository

To clone a GitHub repository, get the clone URL as described in Cloning a repository.

For an overview of the Git workflow, see Azure Repos Git tutorial.

Prerequisites

• Repos must be enabled in your Azure DevOps project settings. If the Repos hub and associated pages don't display, see Turn an Azure DevOps service on or off to reenable Repos.

• To view code in private projects, you must be a member of an Azure DevOps project with Basic access level or higher. For public projects, everyone can view the code.

  • If you don't have a project, create one or sign up for free.

  • If you aren't a project member, get added.

• To clone or contribute to code for a private project, you must be a member of the Contributors security group or have the corresponding permissions set. For public projects, anyone can clone and contribute code. For more information, see What is a public project?

  Note

  For public projects, users granted Stakeholder access have full access to Azure Repos.

For more information about permissions and access, see Default Git repository and branch permissions and About access levels.

Note

Visual Studio 2019 version 16.8 and later versions provide a new Git menu for managing the Git workflow with less context switching than Team Explorer. Procedures provided in this article under the Visual Studio tab provide information for using the Git experience as well as Team Explorer. For more information, see Side-by-side comparison of Git and Team Explorer.

Add a project or solution to a new local Git repository

The first step to sharing your Visual Studio solution with others using Git is to create a local Git repo for your code. If it's your first time using Visual Studio to connect to Azure Repos, see Connect to a project from Visual Studio for details.

Visual Studio 2022

1. Create a new local Git repo for your Visual Studio solution, by right-clicking the solution name in Solution Explorer, and then selecting Create Git Repository. Or, choose Add to Source Control on the status bar in the lower right-hand corner of Visual Studio, and then select Git. If you don't see these options, then your code is already in a Git repo.

   

   Or, choose Git > Create Git Repository from the menu bar to launch the Create a Git repository window. If you don't see this option, then your code is already in a Git repo.

   

2. This step only applies to the Visual Studio Git version control experience: in the Create a Git repository window, choose Local only, verify the local path is correct, and then choose Create.

   

You've now created a local Git repo in the Visual Studio solution folder and committed your code into that repo. Your local Git repo contains both your Visual Studio solution and Git resources.

Visual Studio 2019 - Git menu

1. Create a new local Git repo for your Visual Studio solution, by right-clicking the solution name in Solution Explorer, and then selecting Create Git Repository. Or, choose Add to Source Control on the status bar in the lower right-hand corner of Visual Studio, and then select Git. If you don't see these options, then your code is already in a Git repo.

   

   Or, choose Git > Create Git Repository from the menu bar to launch the Create a Git repository window. If you don't see this option, then your code is already in a Git repo.

   

2. This step only applies to the Visual Studio Git version control experience: in the Create a Git repository window, choose Local only, verify the local path is correct, and then choose Create.

   

You've now created a local Git repo in the Visual Studio solution folder and committed your code into that repo. Your local Git repo contains both your Visual Studio solution and Git resources.

Visual Studio 2019 - Team Explorer

These tasks are not supported through Team Explorer.

Git Command Line

1. Download and install Git. When prompted during the install, enable Git Credential Manager.

2. At the command prompt, go to the root folder that contains your Visual Studio solution and run the following commands. These commands create a local Git repo in the Visual Studio solution folder and commit your code into that repo.

   > git init
   > git commit -am "first commit"
   > git branch -m main
   

   Your local Git repo now contains both your Visual Studio solution and Git resources.

   

Publish your code

You can share your work with others by publishing your local Git repo to an Azure Repos Git repo.

Visual Studio 2022

Visual Studio 2022 provides a Git version control experience by using the Git menu, Git Changes, and through context menus in Solution Explorer. Visual Studio 2019 version 16.8 also offers the Team Explorer Git user interface. For more information, see the Visual Studio 2019 - Team Explorer tab.

1. Connect to an Azure DevOps repo by right-clicking the solution name in Solution Explorer, and then selecting Push to Git service to launch the Create a Git repository window.

   

   Or, choose Git > Push to Git service from the menu bar to launch the Create a Git repository window.

   

2. In the Create a Git repository dialog, select GitHub. Enter any required values under Create a new GitHub repository. Then select Push.

   

   You can verify that the repo is created by going to GitHub and searching for your repo name in your account.

Visual Studio 2019 - Git menu

Visual Studio 2019 provides a Git version control experience by using the Git menu, Git Changes, and through context menus in Solution Explorer.

1. Connect to an Azure DevOps repo by right-clicking the solution name in Solution Explorer, and then selecting Push to Git service to launch the Create a Git repository window.

   

   Or, choose Git > Push to Git service from the menu bar to launch the Create a Git repository window.

   

2. Open a browser and navigate to your Azure DevOps project by using a URL in the form of https://dev.azure.com/<OrganizationName>/<ProjectName>. If you don't have a project yet, create one.

3. In your Azure DevOps project, Create an empty Git repo without a README file. Copy the clone URL from the Clone Repository popup.

   

4. In the Create a Git repository window, choose Existing remote and enter the repo clone URL from the previous step, and then choose Push. For more information on how to create a new Azure DevOps repo, see Create a new Git repo in your project.

   

5. The Git Changes window shows a confirmation message that your code is now in an Azure DevOps repo.

   

Note

With Azure DevOps Services, the format for the project URL is dev.azure.com/{your organization}/{your project}. However, the previous format that references the visualstudio.com format is still supported. For more information, see Introducing Azure DevOps, Switch existing organizations to use the new domain name URL.

Visual Studio 2019 - Team Explorer

Visual Studio 2019 version 16.8 and later versions provides a Git version control experience while maintaining the Team Explorer Git user interface. To use Team Explorer, uncheck Tools > Options > Preview Features > New Git user experience from the menu bar. You can exercise Git features from either interface interchangeably. Below, we provide a side-by-side comparison for publishing your code.

Note

One advantage of connecting to a project through Team Explorer is you gain access to the Work Items hub. For an overview of Team Explorer features, see Navigate in Visual Studio Team Explorer.

1. In the Push to Azure Dev Ops Services section of the Synchronization view in Team Explorer, select the Publish Git Repo button.

   

2. Choose your Azure DevOps organization and repo name, and then select Publish Repository.

   

   This step creates a new project with the same name that you selected for the repo. To create the repo in an existing project, select Advanced next to the Repository name, and then choose a project.
   
   

3. Your code is now in a Azure Repos Git repository. You can view your code on the web by selecting See it on the web.

   

Note

With Azure DevOps Services, the format for the project URL is dev.azure.com/{your organization}/{your project}. However, the previous format that references the visualstudio.com format is still supported. For more information, see Introducing Azure DevOps, Switch existing organizations to use the new domain name URL.

Git Command Line

1. Open a browser and navigate to your Azure DevOps project using a URL in the form of https://dev.azure.com/<OrganizationName>/<ProjectName>. If you don't have a project yet, create one.

2. In your Azure DevOps project, create an empty Git repo without a README file. Copy the clone URL from the Clone Repository popup.

   

3. To publish your local commit to Azure repos, run the following commands at the command prompt in your local git repo folder, using the clone URL from the previous step.

   > git remote add origin <clone URL>
   > git push -u origin main
   

   Your code is now published to the main branch of an Azure Repos Git repository.

Note

With Azure DevOps Services, the format for the project URL is dev.azure.com/{your organization}/{your project}. However, the previous format that references the visualstudio.com format is still supported. For more information, see Introducing Azure DevOps, Switch existing organizations to use the new domain name URL.

Review commit changes

It's good practice to review the code changes in your commit before publishing. Visual Studio provides a diff view that helps you see all the changes you've made since the previous commit.

Visual Studio 2022

1. To see what's changed in a commit, select Git > Manage Branches to open the Git Repository window.

   

2. In the Git Repository window, select your branch, right-click the commit, and then choose View Commit Details to open the Commit window.

   

3. In the Commit window, you can right-click on any file and select Compare with Previous to view the file changes made by the commit.

   

Visual Studio 2019 - Git menu

1. To see what's changed in a commit, select Git > Manage Branches to open the Git Repository window.

   

2. In the Git Repository window, select your branch, right-click the commit, and then choose View Commit Details to open the Commit window.

   

3. In the Commit window, you can right-click on any file and select Compare with Previous to view the file changes made by the commit.

   

Visual Studio 2019 - Team Explorer

1. To see what's changed in a commit, go to the Synchronization page in Team Explorer, right-click on any commit, and then choose View Commit Details to open the Git Details window.

   

2. In the Commit Details window, you can right-click on any file and select Compare with Previous to view the file changes made by the commit.

   

Git Command Line

To show a diff view of the last commit in your current branch, run the following command at the command prompt in your local git repo folder.

> git show

Link work items to your commits

As you develop your software, you can capture which commits support the completion of work items like Azure DevOps tasks or bug fixes. The audit trail of work items linked to commits lets your team understand how tasks and bugs were resolved.

Note

The #ID syntax is supported when you connect to an Azure Repos Git repository. If you connect to a GitHub repository, you can still link to work items, but must use the #ABID syntax, and have previously set up an Azure Boards-GitHub connection.

Visual Studio 2022

You can link work items to commits by adding #ID into the commit message. For example, the commit message "Fix bug #12 Missing icons in the reporting tools" would link work item 12 to the commit when the commit is pushed to Azure Repos.

Visual Studio 2019 - Git menu

You can link work items to commits by adding #ID into the commit message. For example, the commit message "Fix bug #12 Missing icons in the reporting tools" would link work item 12 to the commit when the commit is pushed to Azure Repos.

Visual Studio 2019 - Team Explorer

You can include work items in your commits through Related Work Items in the Changes view of Team Explorer.

You can also link work items to commits by adding #ID into the commit message. For example, the commit message "Fix bug #12 in the reporting tools" would link work item 12 to the commit when the commit is pushed to Azure Repos.

Git Command Line

You can link work items to commits by adding #ID into the commit message. For example, the commit message "Fix bug #12 in the reporting tools" would link work item 12 to the commit when the commit is pushed to Azure Repos. To test, make some code changes and run the following commands at the command prompt in your local git repo folder.

> git commit -am "Fix bug #<work item ID>"
> git push

Push commit changes

Visual Studio 2022

As you write your code, your changes are automatically tracked by Visual Studio. When you're satisfied with your changes, you can save them in Git using a commit, and then push your commit to Azure Repos.

1. In the Git Changes window, enter a message that describes the changes, and then choose Commit All. Commit All commits unstaged changes and skips the staging area. You can choose to stage all files before committing by selecting the stage all + (plus) button at the top of the Changes section of the Git Changes window.

   

2. To push your commit to Azure Repos, select the up-arrow push button.

   

   Or, you can push your commit from the Git Repository window. To open the Git Repository window, select the outgoing / incoming link in the Git Changes window.

   

   Or, you can choose Git > Push from the menu bar.

   

Visual Studio 2019 - Git menu

As you write your code, your changes are automatically tracked by Visual Studio. When you're satisfied with your changes, you can save them in Git using a commit, and then push your commit to Azure Repos.

1. In the Git Changes window, enter a message that describes the changes, and then choose Commit All. Commit All commits unstaged changes and skips the staging area. You can choose to stage all files before committing by selecting the stage all + (plus) button at the top of the Changes section of the Git Changes window.

   

2. To push your commit to Azure Repos, select the up-arrow push button.

   

   Or, you can push your commit from the Git Repository window. To open the Git Repository window, select the outgoing / incoming link in the Git Changes window.

   

   Or, you can choose Git > Push from the menu bar.

   

Visual Studio 2019 - Team Explorer

As you write your code, your changes are automatically tracked by Visual Studio. When you're satisfied with your changes, you can save them in Git using a commit, and then push your commit to Azure Repos.

1. Open the Changes view of Team Explorer by selecting the Home button and choosing Changes. Or, select the pending changes icon on the status bar.

   

2. In the Git Changes window, enter a message that describes the changes, and then choose Commit All. Commit All commits unstaged changes and skips the staging area. You can choose to stage all files before committing by selecting the stage all + (plus) button at the top of the Changes section in the Git Changes window.

   

3. To push one or more commits to Azure Repos, select Home and then choose Sync to open the Synchronization view in Team Explorer. Or, select the unpublished changes status bar icon ( on the status bar.

   

4. In the Synchronization view, choose Push to upload your commit to the remote repo. If this is your first push to the repo, you'll see the message: The current branch does not track a remote branch..., which lets you know that your commit was pushed to a new branch on the remote repo and that future commits pushed from the current branch will be uploaded to that remote branch.

   

Git Command Line

To publish new commits from your current local branch to the corresponding branch in the Azure Repos Git repo, run the following command at the command prompt in your local git repo folder.

> git push

Pull changes

You can keep your local branches in sync with their remote counterparts by pulling commits created by others. While you're working on your feature branch, it's a good idea to periodically switch to your main branch and pull new commits to keep it current with the remote main branch.

Note

In Visual Studio, Fetch and Pull links can be found in different views and in the Git menu on the menu bar. Those links all do the same thing—fetch or pull from the remote repo to the current branch of the local repo.

Visual Studio 2022

1. In the Git Changes window, you can check for the latest commits on the remote branch by using the down-arrow fetch link, then selecting the outgoing / incoming link to open the Git Repository window. Fetch downloads remote commits that aren't in your local branch, but won't merge them into your local branch. Fetched commits show up in the Incoming Commits section of the Git Repository window. You can double-click a fetched commit to view its file changes.

   

2. Choose Pull to merge the fetched remote commits into your local repo. Pull performs a fetch and then merges the downloaded commits into your local branch.

Visual Studio 2019 - Git menu

1. In the Git Changes window, you can check for the latest commits on the remote branch by using the down-arrow fetch link, then selecting the outgoing / incoming link to open the Git Repository window. Fetch downloads remote commits that aren't in your local branch, but won't merge them into your local branch. Fetched commits show up in the Incoming Commits section of the Git Repository window. You can double-click a fetched commit to view its file changes.

   

2. Choose Pull to merge the fetched remote commits into your local repo. Pull performs a fetch and then merges the downloaded commits into your local branch.

Visual Studio 2019 - Team Explorer

1. In Team Explorer, select Home and choose Sync to open the Synchronization view.

   

2. In the Synchronization view, you can preview the latest changes on the remote branch by using the Fetch link. Fetch downloads remote commits that aren't in your local branch, but doesn't merge them. Fetched commits show up in the Incoming Commits section of the Synchronization view. You can double-click a commit to view its file changes.

   

3. Choose Pull to merge the fetched remote commits into your local repo. Pull performs a fetch and then merges the downloaded commits into your local branch.

Git Command Line

To download new commits from the Azure Repos Git repo without merging them into your local repo, run the following command at the command prompt in your local git repo folder.

> git fetch

To download and merge new commits from the Azure Repos Git repo into the current branch of your local repo, run the following command.

> git pull

FAQs

Q: Why does the sign-in page differ between the web portal and Visual Studio?

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

Q: Can I use the Git command prompt with Visual Studio?

A: Visual Studio's Team Explorer and the Git command-line work great together. Changes to your repos made in either tool will be reflected in the other. Make sure to install the latest release of Git for Windows, which has tools to help you connect to your Azure DevOps Services/TFS repos.

See the Azure Repos Git tutorial and the command reference for additional help using Git from the command line.

Next steps

Set up a build Azure Repos Git tutorial

Related articles

• New to Git repos? Learn more