/azure-devops

name: azure-devops
description: Interact with Azure DevOps repositories, pull requests, and APIs using the AZURE_DEVOPS_TOKEN environment variable. Use when working with code hosted on Azure DevOps or managing Azure DevOps resources.
triggers:
- azure_devops
- azure

Connection selection

Use authenticated Azure DevOps MCP tools first when they are available in the agent's environment. Detect this by tool availability, without depending on a particular MCP server name. Use the token and direct API instructions below only when Azure DevOps MCP tools are unavailable or when raw API or `curl` access is explicitly needed.

You have access to an environment variable, `AZURE_DEVOPS_TOKEN`, which allows you to interact with the Azure DevOps API.

<IMPORTANT> You can use `curl` with the `AZURE_DEVOPS_TOKEN` to interact with Azure DevOps's API. ALWAYS use the Azure DevOps API for operations instead of a web browser. </IMPORTANT>

If you encounter authentication issues when pushing to Azure DevOps (such as password prompts or permission errors), the old token may have expired. In such case, update the remote URL to include the current token: `git remote set-url origin https://${AZURE_DEVOPS_TOKEN}@dev.azure.com/organization/project/_git/repository`

Here are some instructions for pushing, but ONLY do this if the user asks you to:

• NEVER push directly to the `main` or `master` branch
• Git config (username and email) is pre-set. Do not modify.
• You may already be on a branch starting with `openhands-workspace`. Create a new branch with a better name before pushing.
• Once you've created your own branch or a pull request, continue to update it. Do NOT create a new one unless you are explicitly asked to. Update the PR title and description as necessary, but don't change the branch name.
• Use the main branch as the base branch, unless the user requests otherwise
• After opening or updating a pull request, send the user a short message with a link to the pull request.
• Do NOT mark a pull request as ready to review unless the user explicitly says so
• Do all of the above in as few steps as possible. E.g. you could push changes with one step by running the following bash commands:

git remote -v && git branch # to find the current org, repo and branch
git checkout -b create-widget && git add . && git commit -m "Create widget" && git push -u origin create-widget

On Windows PowerShell, run those `git` commands as separate commands if `&&` is not supported by the installed shell.

Azure DevOps API Usage

When working with Azure DevOps API, you need to use Basic authentication with your Personal Access Token (PAT). The username is ignored (empty string), and the password is the PAT.

Here's how to authenticate with curl:

# Convert PAT to base64
AUTH=$(echo -n ":$AZURE_DEVOPS_TOKEN" | base64)

# Make API call
curl -H "Authorization: Basic $AUTH" -H "Content-Type: application/json" https://dev.azure.com/{organization}/{project}/_apis/git/repositories?api-version=7.1

PowerShell equivalent for the PAT header:

$auth = [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes(":$env:AZURE_DEVOPS_TOKEN"))
Invoke-RestMethod `
  -Headers @{ Authorization = "Basic $auth"; "Content-Type" = "application/json" } `
  -Uri "https://dev.azure.com/{organization}/{project}/_apis/git/repositories?api-version=7.1"

Common API endpoints:

• List repositories: `https://dev.azure.com/{organization}/{project}/_apis/git/repositories?api-version=7.1`
• Get repository details: `https://dev.azure.com/{organization}/{project}/_apis/git/repositories/{repositoryId}?api-version=7.1`
• List pull requests: `https://dev.azure.com/{organization}/{project}/_apis/git/pullrequests?api-version=7.1`
• Create pull request: `https://dev.azure.com/{organization}/{project}/_apis/git/repositories/{repositoryId}/pullrequests?api-version=7.1` (POST)