Share your code with Azure Repos and Visual Studio

Create a new local Git repo for your project by selecting on the status bar in the lower right hand corner of Visual Studio. This will create a new repo in the folder the solution is in and commit your code into that repo. You can also right-click your solution in Solution Explorer and choose Add Solution to Source Control.

Once you have a local repo, select items in the status bar to quickly navigate between Git tasks in Team Explorer.

• shows the number of unpublished commits in your local branch. Selecting this opens the Synchronization view in Team Explorer.
• shows the number of uncommitted file changes. Selecting this opens the Changes view in Team Explorer.
• shows the current Git repo. Selecting this opens the Connect view in Team Explorer.
• shows your current Git branch. Selecting this displays a branch picker to quickly switch between Git branches or create new branches.

Create a new local Git repo for your project by selecting on the status bar in the lower right hand corner of Visual Studio. This will create a new repo in the folder the solution is in and commit your code into that repo.

Once you have a local repo, select items in the status bar to quickly navigate between Git tasks in Team Explorer.

• shows the number of unpublished commits in your local branch. Selecting this will open the Sync view in Team Explorer.
• shows the number of uncommitted file changes. Selecting this will open the Changes view in Team Explorer.
• shows the current Git repo. Selecting this will open the Connect view in Team Explorer.
• shows your current Git branch. Selecting this displays a branch picker to quickly switch between Git branches or create new branches.

Open your project in Visual Studio

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

   • Sign up and create your project.
   • Install Visual Studio 2013 or later.

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

   

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

Clone your repository

1. Clone the repository onto your dev machine.

   

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

   

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

   

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.

   

   

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

   

1. Navigate to the Push view in Team Explorer by choosing the icon in the status bar. You can also select Sync from the Home view in Team Explorer.

2. In the Push view in Team Explorer, select the Publish Git Repo button under Push to Visual Studio Team Services.

   

3. Verify your email and select your account in the Team Services Domain drop-down.

4. Enter your repository name and select Publish repository.

   

   This creates a new project in your account with the same name as the repository. To create the repo in an existing project, click Advanced next to Repository name and select a project.

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

   

1. In the Sync view in Team Explorer, select the Publish Git Repo button under Publish to Azure Repos.

   

2. Verify your email and select your account in the Account Url drop down.

3. Enter your repository name and select Publish Repository.

   

   This creates a new Project in your account with the same name as the repository. To create the repo in an existing Project, click Advanced next to Repository name and select a project.

   Note

   The Publish link in the status bar ( ) was added in Visual Studio 2015 Update 2 and will only appear when you have Git as your source control provider. If your code is already in a Git repo, you won't see the Publish button in the status bar, but the information from your local repo instead.

   If you are in a previous version of Visual Studio, create a local Git repo for your project by selecting the Create new Git repository option in the New Project window when you create a new project. You can create a local Git repo for an existing solution by right-clicking your project in the Solution Explorer and selecting Add Solution to Source Control.

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

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.

   

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

   

3. Push your changes.

   

• To see what's changed in a commit, go to the Synchronization page in Team Explorer and right-click on the commit. Select View Commit Details. You can then right-click on any file modified by the commit and select Compare with Previous... to view the changes compared to the previous version of the file.

  

• To see what's changed in a commit, go to the Synchronization page in Team Explorer and right-click on the commit. Select View Commit Details. You can then right-click on any file modified by the commit and select Compare with Previous... to view the changes compared to the previous version of the file.

  

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

  

• To review information about the commits from your team before you pull them:

  

• To get details on the changes to each file.

  

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

  

  Also, you can include work items in commits by adding #ID into the commit message. For example, "Fixing bug #23 in the reporting tools" would link work item 23 to the commit. The work item is linked when the commit is pushed to Azure Repos.

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

  

  Also, you can include work items in commits by adding #ID into the commit message. For example, "Fixing bug #23 in the reporting tools" would link work item 23 to the commit. The work item is linked when the commit is pushed to Azure Repos.

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

  

1. As you write your code, your changes are automatically tracked by Visual Studio. You can commit changes to your local Git repository by selecting the pending changes icon from the status bar.

2. On the Changes view in Team Explorer, add a message describing your update and commit your changes.

   

3. Select the unpublished changes status bar icon (or select Sync from the Home view in Team Explorer). Select Push to update your code in Azure DevOps Services/TFS.

   

1. As you write your code, your changes are automatically tracked by Visual Studio. You can commit changes to your local Git repository by selecting the pending changes icon ( ) from the status bar.

2. On the Changes view in Team Explorer, add a message describing your update and commit your changes.

   

3. Select the unpublished changes status bar icon ( ) or the Sync view in Team Explorer. Select Push to update your code in Azure DevOps Services/TFS.

   

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

   

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

   

   These changes are now committed.

   

3. 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. From the changes page (Keyboard: Ctrl + 0, G), make sure you've committed your changes.

   

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

   

5. Push your changes.

   

Sync your local repo with changes from your team as they make updates.

1. From the Synchronization view in Team Explorer, fetch the commits that your team has made. Double-click a commit to view its file changes.

   

2. Select Sync to merge the fetched commits into your local repo and then push any unpublished changes to Azure Repos.

   

3. The changes from your team are now in your local repo and visible in Visual Studio.

Sync your local repo with changes from your team as they make updates.

1. From the Sync view in Team Explorer, fetch the commits that your team has made. Double-click a commit to view its file changes.

   

2. Select Sync to merge the fetched commits into your local repo and then push any unpublished changes to Azure Repos.

   

3. The changes from your team are now in your local repo and visible in Visual Studio.

   

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.

   

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

   

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