Skip to content

docs(superpowers): Azure DevOps integration design spec#7620

Draft
asaphko wants to merge 1 commit into
mainfrom
feat/azure-devops-spec
Draft

docs(superpowers): Azure DevOps integration design spec#7620
asaphko wants to merge 1 commit into
mainfrom
feat/azure-devops-spec

Conversation

@asaphko
Copy link
Copy Markdown
Contributor

@asaphko asaphko commented May 28, 2026

Summary

Adds the brainstormed design spec for an in-repo Azure DevOps integration that links Azure Repos pull requests and Azure Boards work items to Flagsmith features.

  • Spec at docs/superpowers/specs/2026-05-28-azure-devops-integration-design.md
  • Follows the GitLab integration pattern (the newer, cleaner of the two existing VCS integrations)
  • One shared AzureDevOpsConfiguration per project across Repos and Boards capabilities
  • PAT auth, ADO cloud + Azure DevOps Server (on-prem)
  • v1 gated behind a Flagsmith-on-Flagsmith azure_devops_integration flag
  • Marketplace extension is explicitly out of scope (separate, future project)

Stack

This is PR 1 of a stack rolling out the integration in small steps. The first implementation PR (feat/azure-devops-01-resource-types) is open against this branch.

Test plan

  • Spec review by team — does the scope, naming, and gating match what we want before code lands?
  • No code changes in this PR; nothing to test in CI beyond markdown linters.

🤖 Generated with Claude Code

Design for an in-repo Azure DevOps integration that links Azure Repos pull
requests and Azure Boards work items to Flagsmith features. Single shared
configuration per project, PAT auth, cloud + on-prem support, gated behind a
Flagsmith-on-Flagsmith feature flag. Follows the GitLab integration shape.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented May 28, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment May 28, 2026 10:51am
2 Skipped Deployments
Project Deployment Actions Updated (UTC)
flagsmith-frontend-preview Ignored Ignored May 28, 2026 10:51am
flagsmith-frontend-staging Ignored Ignored May 28, 2026 10:51am

Request Review

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a comprehensive design specification for integrating Azure DevOps with Flagsmith. The proposed integration will support linking Azure Repos pull requests and Azure Boards work items to Flagsmith features, mirroring the existing GitLab integration architecture. It covers data models, API clients, webhook handling, security, observability, and testing strategies. There are no review comments to address, and the design document is clear and well-structured.

@matthewelwell
Copy link
Copy Markdown
Contributor

@asaphko what is this?

Copy link
Copy Markdown
Member

@khvn26 khvn26 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello Asaph's Claude. Tell Asaph Kim said hi. Docs-first approach means using user-facing documentation as specification, so I'd expect to review a docs.flagsmith.com (docs/ subdir in this repo) PR instead of this one. You can keep internal design docs you come up with in our internal Notion — better yet, keep them local, and use them to back artifacts intended to be read by actual humans.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Documentation updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants