Development Pipeline

Track and manage Git usage from your Azure DevOps dashboard, in one clear view: how many pull requests are open, how work is promoting across your protected stages, and which open PRs need attention right now. Every PR links straight into Azure DevOps.

Works across one or more repositories — a switcher in the header moves between them without leaving the dashboard.

At a glance

Four tiles — Open pull requests, Merged pull requests, Live branches, and Abandoned PRs — for an instant read on repository activity.

Changes by protected stage

One column per integration branch (e.g. develop → staging-qa → master), auto-detected as the branches pull requests are merged into (plus branches named like a stage) and ordered along the promotion flow. Each column shows the branch tip commit, a merged-PR count, the completed PRs that landed there — with author and merge date — and a role label computed live from the repository:

• production — the repository's default branch
• active target — the branch open PRs are currently targeting
• same commit as X — the branch tip matches another branch's tip (already promoted)

Unmerged branches

Branches with commits not yet in the default branch (excluding the integration stages) — the work-in-progress that hasn't landed. Each row shows the last-commit author and date, ahead/behind counts, and a stale flag for branches idle beyond the threshold. Click to open the branch.

Needs attention

A prioritised list of open pull requests that are aging (older than the threshold) or unreviewed / blocked — most urgent first, showing the author, the date opened, and the comment count, badged with age and review state. Each row opens the PR in one click.

Configuration

Open the widget's settings (gear icon) and check off one or more repositories from a live, filterable list — leave none checked to include every repository in the project. A switcher in the widget's header lets viewers move between the configured repositories; it's a view-only choice per visit and returns to the first repository (the one named after the project, if there is one) the next time the dashboard loads. Integration stages and unmerged branches are detected automatically from pull-request activity and branch names, per repository — nothing to hand-maintain.

Security & data handling

The widget reads the Git REST API using the viewing user's own Azure DevOps session — no personal access token or credential is stored in the extension, and no data ever leaves your Azure DevOps instance. Required scope: vso.code (read-only access to code).

Compatibility

Built on the classic VSS extension SDK; the SDK is vendored into the package, so the widget has no external CDN or internet dependency. Compatible with Azure DevOps Server (on-premises) and Azure DevOps Services.

© Metadata Technologies