Skip to content
Changelog

Taiga on Azure DevOps

Connect Azure DevOps, and products in Azure Repos are planned, built, reviewed and merged under your branch policies, with Azure Pipelines deployments on the Deployments page.

Organizations standardised on Microsoft keep their code in Azure Repos and ship it with Azure Pipelines. Taiga reached GitHub and GitLab, and that code stayed out of reach.

Azure DevOps Services now sits beside them. Connect your organization once, link a repository to a product, and the whole cycle runs there: Taiga pushes its branch, opens the pull request, works through failed validation builds and answers review threads. Your branch policies decide when it merges. With autonomous merge on, Taiga completes a pull request only once its required reviewers, resolved comments and validation build are in place. The work is done by a dedicated account you create, so your history shows Taiga, not a colleague.

Deployments to your Azure environments appear on the product's Deployments page, read from the pipelines' own history.

A team whose main branch requires two reviewers and a green build gets pull requests that wait for both, then complete without anyone pressing the button.

Teams on Microsoft's stack now get the same Taiga as everyone else.

Also in Administration
  • Azure DevOps is open to every organization, with nothing to request

Connect Azure DevOps →

Every change, dated the day it shipped.

Dated the day they shipped, newest first.