Azure DevOps Integration for VS Code

A VS Code extension for Azure DevOps. Browse pull requests in a sidebar grouped by "Created by me," "Assigned to me," and "My teams," with review, check, and comment status. Auto-detects config from git remotes and extracts work item IDs from branch names. Create PRs, open repos, and link work items — all without leaving the editor.

Features

Pull Request Sidebar

View your assigned pull requests directly in the Activity Bar. PRs are grouped into three categories:

• Created by me — PRs you authored
• Assigned to me — PRs where you're a reviewer
• Assigned to my teams — PRs assigned to teams you belong to

Each PR displays rich status information:

• Draft indicator
• Source branch
• Author and reviewer names
• Review status (Approved / Waiting / Rejected)
• Check status (Passed / Failed / Running)
• Unresolved comment count

Click any PR to open its changes in VS Code. Use the context menu to open the PR in Azure DevOps when needed.

Work Item Detection

The extension automatically extracts work item IDs from your branch name using common patterns:

• AB#1234
• feature/1234-description
• 1234-description
• bugfix/1234-description

The detected work item is shown in the status bar (e.g., WI [#1234](https://github.com/lucacelea/azure-devops-integration-plugin/issues/1234)) and clicking it opens the work item in Azure DevOps.

Commands

Open the Command Palette (Cmd+Shift+P) and type "Azure DevOps" to access:

Getting Started

1. Install the Extension

Install from the VS Code Marketplace or search for "Azure DevOps Integration" in the Extensions view.

2. Set Up Authentication

1. Generate a Personal Access Token (PAT) in Azure DevOps with the following scopes:
   • Code: Read
   • Work Items: Read
   • Project and Team: Read
2. Run the command Azure DevOps: Set Personal Access Token and paste your token.

Your PAT is stored securely using VS Code's built-in SecretStorage API.

3. Open a Repository

Open a folder that has an Azure DevOps git remote. The extension auto-detects your organization, project, and repository from the remote URL.

Supported remote formats:

• https://dev.azure.com/{org}/{project}/_git/{repo}
• https://{org}.visualstudio.com/{project}/_git/{repo}
• git@ssh.dev.azure.com:v3/{org}/{project}/{repo}

Configuration

All settings are optional — the extension auto-detects values from your git remote.

Requirements

• VS Code 1.85.0 or later
• An Azure DevOps account with a Personal Access Token

Development

CI checks

GitHub Actions runs compile, lint, and test on every pull request and on pushes to main.

Releases

Releases are published from GitHub Actions when you push a version tag:

1. Update package.json and CHANGELOG.md
2. Commit and push to main
3. Create and push a tag that matches the package version, for example v0.3.0

The release workflow will:

• verify the tag matches package.json
• run compile, lint, and tests
• build a .vsix
• publish the extension to the Visual Studio Marketplace
• upload the .vsix to the GitHub Actions run and the GitHub release

Required GitHub secret:

• VSCE_PAT: Visual Studio Marketplace personal access token for the lucacelea publisher

Branch protection

In GitHub repository settings, protect main and require the Build and Test status check before merging pull requests.

Recommended settings:

• require pull requests before merging
• require status checks to pass before merging
• select the Build and Test check from the CI workflow
• require branches to be up to date before merging
• restrict direct pushes to main

See CONTRIBUTING.md for the local development and PR flow.

License

MIT