แชร์ผ่าน


Share your code with Azure Repos and Visual Studio

TFS 2017 | TFS 2015

Visual Studio 2019 | Visual Studio 2017 | Visual Studio 2015 | Visual Studio 2013

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

  • To view code, you must be a member of an Azure DevOps project with Basic access or higher. If you aren't a project member, get added.

  • To clone or contribute to code, you must be a member of the Contributors security group or have the corresponding permissions.

To learn more 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 2019 tab provide information for using the Git experience as well as Team Explorer. To learn more, 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.

  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.

    Screenshot of the 'Create Git repository' option in the Solution Explorer context menu in Visual Studio 2019.

    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.

    Screenshot of the 'Create Git Repository' option in the Git menu from the menu bar of Visual Studio 2019.

  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.

    Screenshot of the 'Create a Git repository' window with the 'Local only' option selected in Visual Studio 2019.

    Team Explorer doesn't launch the Create a Git repository window, and assumes you want a local Git repo.

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.

Screenshot of the Git folder, Git ignore file, and Git attributes file in Windows file explorer.

Publish your code

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

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.

Visual Studio Git

  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.

Screenshot of the 'Push to Git service' menu option in the Git menu on the menu bar in Visual Studio 2019.

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

Screenshot of the 'Push to Git service' option in the in Visual Studio 2019 context menu.

  1. 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.

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

Screenshot of the 'Clone Repository' popup from the Azure DevOps project site.

  1. 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.

Screenshot of the 'Create a Git repository' window, with the URL of an empty Azure repo, in Visual Studio 2019.

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

Screenshot of the 'Git Changes' window, with a confirmation message that your code is in 'Azure DevOps' repo, in Visual Studio 2019.

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.

Screenshot of the 'Push' view of 'Team Explorer' in Visual Studio 2019.

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

Screenshot of the Azure DevOps account, organization, and repo name options and the 'Publish Repository' button in the 'Synchronization' view of 'Team Explorer' in Visual Studio 2019.

This step creates a new project in your Azure DevOps account 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.

  1. 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.

Screenshot of the 'See it on the web' link in the 'Home' view of 'Team Explorer' in Visual Studio 2019.

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 Git

  1. To see what's changed in a commit, open the Git Repository window by choosing Git > Manage Branches from the menu bar.

Screenshot of in Visual Studio 2019.

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

Screenshot of the 'View Commit Details' menu option for a commit in the 'Git Repository' window in Visual Studio 2019.

  1. 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.

Screenshot of the 'Compare with Previous' option in the Commit pane in Visual Studio 2019.

Visual Studio 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.

Screenshot of a commit in the Synchronization view of Team Explorer in Visual Studio 2019.

  1. 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.

Screenshot of the 'Compare with Previous' option in the 'Commit Details' window in Visual Studio 2019.

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 Git

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.

Screenshot of a work item linked to a commit in the 'Git Changes' window in Visual Studio 2019.

Visual Studio Team Explorer

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

Screenshot of a work item linked to a commit in the Changes view of Team Explorer in Visual Studio 2019.

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.

Push commit changes

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.

Visual Studio Git

  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.

Screenshot of the 'Commit All' button in the 'Git Changes' window in Visual Studio 2019.

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

Screenshot of the up-arrow push button in the 'Git Changes' window of Visual Studio 2019.

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.

Screenshot of the 'outgoing / incoming' link in the 'Git Changes' window, and the Push link in the 'Git Repository' window of Visual Studio 2019.

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

Screenshot of the Push option from the Git menu in Visual Studio 2019.

Visual Studio Team Explorer

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

Screenshot of the Changes option in Team Explorer in Visual Studio 2019.

  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 in the Git Changes window.

Screenshot of the 'Screenshot of commit message text and 'Commit All' button in Visual Studio 2019.

  1. 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 (Visual Studio unpublished changes status bar icon on the status bar.

Screenshot of the Sync option in Team Explorer in Visual Studio 2019.

  1. 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.

Screenshot of the Push link in the Synchronization view of Team Explorer in Visual Studio 2019.

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

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 Git

  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.

Screenshot of the Fetch, Pull, Push and Sync buttons in the 'Git Changes' window of Visual Studio 2019.

  1. 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 Team Explorer

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

Screenshot of the Sync option in 'Team Explorer' in Visual Studio 2019.

  1. 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.

Screenshot of the Pull link in the Synchronization view of Team Explorer in Visual Studio 2019.

  1. 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.

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 for your code and learn more about using Git in the Azure Repos Git tutorial.