Azure DevOps Pull Review

Browse and review Azure DevOps pull requests without leaving VS Code. Sign in with your existing VS Code account, add one or more ADO organizations, and get a full PR review workflow — diffs, comments, votes, and policy gates — directly in the editor.

Features

• Multi-org support — connect to one or more Azure DevOps organizations simultaneously
• PR list with filtering — filter pull requests by author, reviewer, title, or description
• Side-by-side and inline diffs — toggle between diff modes; markdown files open a rendered preview alongside the diff
• Inline comments — click any gutter line in the diff to start a new comment thread
• Thread management — reply to, resolve, or reactivate existing comment threads
• Voting — approve or reject a PR directly from the tree view context menu
• Policy gates — see all required/optional policy checks and their current status; requeue a failed check with one click
• Auto-detect local repo — when you open a folder cloned from ADO, the extension automatically scopes itself to that repo's org/project/repository
• Checkout PR branch — pull and check out the PR source branch locally from the context menu
• View PR status - double click a PR and view PR overview along with status checks, reviewers

Requirements

• VS Code 1.90 or later
• An Azure DevOps account (cloud dev.azure.com — Microsoft OAuth sign-in is used automatically; on-premises ADO Server requires a Personal Access Token)

Getting Started

1. Install the extension and open the Azure DevOps panel in the activity bar.
2. Click Sign In (or use the command palette: Azure DevOps: Sign In). Your existing VS Code Microsoft account is used; no separate sign-in is needed for cloud ADO.
3. Click the + button in the panel toolbar and enter your organization URL (e.g. https://dev.azure.com/myorg).
4. The tree expands to show your projects and repositories. Browse to a repository to see its open pull requests.

Reviewing a Pull Request

• Double-click a PR node to open the PR detail panel (description, reviewers, policy gates).
• From the detail panel, click any changed file to open it in a side-by-side diff view.
• Click the gutter icon next to any line in the diff to leave a comment.
• Right-click a PR node for quick actions: Approve, Reject, Copy URL, Checkout PR Branch.

Filtering Pull Requests

Click the filter icon in the panel toolbar to filter by:

• Author display name
• Reviewer display name
• Title substring
• Description substring

Context Management

If you open a folder cloned from an ADO remote, the extension auto-detects the organization, project, and repository. Use the filter or command palette to override the active context manually:

• Azure DevOps: Set Active Organization
• Azure DevOps: Set Active Project
• Azure DevOps: Set Active Repository
• Azure DevOps: Reset Context to Local Git Repo — clears any manual override and returns to auto-detect

Extension Settings

Known Limitations

• On-premises ADO Server requires a Personal Access Token; use Azure DevOps: Sign In and enter your PAT when prompted.
• Mention autocomplete (@user, #workitem) in comment boxes works for users. There maybe bugs with workitem.
• When opening workspaces the pull request pane does not auto-expand.
• Markdown diff preview scroll-sync depends on VS Code recognising the diff document language as Markdown; this works when the file extension is .md or .markdown.

Release Process

The repository includes a tag-driven release workflow in .github/workflows/release.yml.

1. Update version in package.json (for example, 0.1.0).
2. Commit and push the change to main.
3. Create and push a matching tag in the format vX.Y.Z (for example, v0.1.0).
4. GitHub Actions builds, lints, tests, packages the extension as a .vsix, and uploads it to the GitHub Release for that tag.

The workflow fails if the pushed tag version does not match package.json version.