如何让Visual Studio同时连接Azure DevOps项目与外部GitHub仓库？

Great question! This is a common pain point when pairing Azure DevOps Boards with an external GitHub repo instead of the built-in Azure Repos. Luckily, there are reliable ways to get both Azure DevOps team features (Work Items, Builds) and full GitHub repo access working side-by-side in Visual Studio.

Method 1: Map Your GitHub Repo While Connected to Azure DevOps #

This is the most straightforward approach, keeping your Azure DevOps team context while working with your GitHub code:

• First, connect to your Azure DevOps team project via Team Explorer (as you normally would) to confirm you can access Work Items, Builds, and other team resources.
• Next, open the Git Changes panel (go to View > Git Changes if it’s not visible). From here, either clone your GitHub repo directly into Visual Studio, or add an existing local GitHub repo folder using the "Add an existing repository" option.
• Once the GitHub repo is loaded, check the Projects and My Teams dropdown in Team Explorer—make sure your Azure DevOps team project is still selected. Visual Studio will now maintain the Azure DevOps connection for team features, while using your GitHub repo for all Git operations (commits, pushes, pulls, etc.).
• Bonus: When you commit code, include your Azure DevOps work item ID in the commit message (e.g., Fix login bug #456), and Azure DevOps will automatically link the commit to the corresponding Work Item.

Method 2: Link Work Items Manually When Using GitHub Repo Directly #

If you prefer connecting directly to your GitHub repo, you don’t have to lose access to Azure DevOps Work Items:

• Connect to your GitHub repo as usual (via the Git Clone dialog or existing repo).
• To access Azure DevOps Work Items, open Team Explorer and switch to the Work Items tab. As long as you’re logged into your Azure DevOps account in Visual Studio, you’ll see all your team’s Work Items, can edit them, and even link them to GitHub commits by referencing the work item ID in your commit message.
• For Builds and Pipelines, you can access them via the Azure DevOps web portal, or add the Azure Pipelines extension in Visual Studio to view pipeline statuses directly in the IDE.

Method 3: Use Azure DevOps CLI to Sync Repo Connections (Advanced) #

For more control, use the Azure DevOps CLI to ensure your local workspace recognizes the GitHub-Azure DevOps link:

1. Install the Azure DevOps CLI extension if you haven’t already:

   az extension add --name azure-devops
   

2. Log in to your Azure DevOps organization:

   az devops login
   

3. Set your default organization and project:

   az devops configure --defaults organization=https://dev.azure.com/your-organization project=your-project-name
   

4. Navigate to your local GitHub repo directory and run:

   az repos git update --name "Your GitHub Repo Display Name" --url https://github.com/your-username/your-repo.git
   

   This ensures Azure DevOps recognizes the repo link, and Visual Studio will pick up this association when connected to your team project.

All these methods let you avoid choosing between Azure DevOps team features and GitHub repo access—you get the best of both worlds.

内容的提问来源于stack exchange，提问作者Lesair Valmont