Add Azure DevOps plugin support (azuredevops_go)

[Copilot]

Adds Azure DevOps as a fully available plugin in the CLI, covering connection creation, interactive org/project/repo scope selection, and PAT resolution.

Registry (cmd/connection_types.go)

• azuredevops_go entry set to Available: true with NeedsOrg, SupportsTest, AuthMethod: "AccessToken", HasRepoScopes: true, ScopeIDField: "id", and PAT env keys AZURE_DEVOPS_PAT / AZDO_PAT
• FindConnectionDef maps legacy alias "azure-devops" → "azuredevops_go"

Scope handler (cmd/configure_scopes.go)

• scopeAzureDevOpsHandler walks the org → project → repo hierarchy via the DevLake remote-scope API
• Interactive multi-select: first pick projects, then repos within each project
• PUTs selected repos via client.PutScopes("azuredevops_go", …)

Tests

• TestAzureDevOpsRegistryEntry — validates all ConnectionDef fields
• TestSelectPlugin_AzureDevOpsAlias — verifies "azure-devops" alias resolves to "azuredevops_go"
• TestAzureDevOpsScopePayload_* — scope payload construction edge cases

Docs

• configure-connection.md: azuredevops_go added to --plugin flag, PAT scopes table (vso.code, vso.build, vso.release), token resolution keys, and connection examples
• configure-scope.md: added to --plugin flag, scope add example, and "What It Does (Azure DevOps)" section covering the two-level project → repo selection flow

# Create connection
gh devlake configure connection --plugin azuredevops_go --org my-org \
    --endpoint https://dev.azure.com/my-org

# Add scopes (interactive project + repo picker)
gh devlake configure scope add --plugin azuredevops_go --org my-org

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[Copilot]

Pull request overview

Updates the CLI documentation for gh devlake configure connection and gh devlake configure scope add to include Azure DevOps (azuredevops_go) usage, including examples and an explanation of the Azure DevOps scoping flow.

Changes:

• Add azuredevops_go to the documented --plugin options for connection and scope commands.
• Document Azure DevOps token env vars and add Azure DevOps connection/scope examples.
• Add an Azure DevOps “What It Does” section describing the interactive project/repo picker behavior.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.

File	Description
docs/configure-scope.md	Adds Azure DevOps to plugin list, provides an Azure DevOps example, and documents the Azure DevOps interactive scoping flow.
docs/configure-connection.md	Adds Azure DevOps to plugin list, documents PAT env vars, adds Azure DevOps examples, and lists Azure DevOps PAT scopes.

[Copilot]

The plugin slug list here looks incomplete vs the actual CLI: availablePluginSlugs() is derived from AvailableConnections() and currently includes additional plugins (e.g., gitlab, bitbucket, jira, sonarqube) beyond the four listed. Please update this list (and any similar lists in this doc) to reflect all supported/available plugins so users aren’t misled.

[Copilot]

--org is documented as “(required for Copilot)” and “GitHub organization slug”, but the code also requires --org for some non-Copilot plugins (e.g., Azure DevOps has NeedsOrg: true) and the meaning differs by plugin. Consider making this description plugin-neutral (and call out Azure DevOps org explicitly) to avoid confusion.

Suggested change

	| `--org` | *(required for Copilot)* | GitHub organization slug |
	| `--org` | *(plugin-dependent)* | Organization identifier. For GitHub/Copilot: GitHub organization slug. For Azure DevOps: Azure DevOps organization name (required when configuring Azure DevOps connections). |

[Copilot]

This doc states Azure DevOps requires PAT scopes vso.code, vso.build, vso.release, but the current connection registry defines RequiredScopes/ScopeHint as empty for azuredevops_go (and tests assert that). Either update the docs to reflect that the CLI doesn’t currently surface required scopes for Azure DevOps, or update the registry/tests so the CLI shows these scopes consistently.

Suggested change

	| `azuredevops_go` | `vso.code`, `vso.build`, `vso.release` |
	| `azuredevops_go` | Azure DevOps PAT (scopes are configured in Azure DevOps; the CLI does not currently validate scopes) |

[Copilot]

The plugin slug list here appears incomplete vs the actual CLI: availablePluginSlugs() comes from AvailableConnections() and includes more than the four listed (e.g., gitlab, bitbucket, jira, sonarqube). If this table is meant to enumerate supported plugins, please update it accordingly (and consider mentioning the supported alias azure-devops for azuredevops_go).

Suggested change

	| `--plugin` | *(interactive or required)* | Plugin to configure (`github`, `gh-copilot`, `jenkins`, `azuredevops_go`) |
	| `--plugin` | *(interactive or required)* | Plugin to configure (e.g., `github`, `gh-copilot`, `jenkins`, `gitlab`, `bitbucket`, `jira`, `sonarqube`, `azuredevops_go` / alias `azure-devops`) |

[Copilot]

--org is described as “GitHub organization slug”, but this command reuses --org for other plugins too (e.g., Azure DevOps organization; GitLab group path). Please make the --org flag description plugin-neutral and/or clarify that its meaning depends on --plugin (you already add an Azure DevOps-specific note later, but the flags table is still GitHub-specific).

[ewega]

@copilot Please address the five review comments on this PR: make the documented plugin slug lists complete/current, make --org descriptions plugin-neutral in both docs, align the Azure DevOps PAT scope wording with the actual CLI behavior/registry, and document the azure-devops alias where relevant. After updating, rerun checks and let the review agent re-check.

[Copilot]

@copilot Please address the five review comments on this PR: make the documented plugin slug lists complete/current, make --org descriptions plugin-neutral in both docs, align the Azure DevOps PAT s...

Addressed in commit 10aa051:

• Plugin slug lists — Both --plugin descriptions now enumerate all 8 available plugins (github, gh-copilot, jenkins, gitlab, bitbucket, jira, sonarqube, azuredevops_go) and note the azure-devops alias.
• --org descriptions — Updated in both files to be plugin-neutral, calling out GitHub org slug, GitLab group path, and Azure DevOps organization name.
• Azure DevOps PAT scopes — Aligned with the registry (RequiredScopes: []string{}): the table now reads "no fixed scopes enforced by the CLI; configure access in Azure DevOps" instead of listing specific vso.* scopes.

[ewega]

Reviewed after follow-up fixes; safe to merge.

[ewega]

Reviewed after follow-up fixes; safe to merge.

[ewega]

@copilot This PR is now merge-conflicted after recent merges. Please rebase/update it onto latest main, resolve the doc overlaps cleanly, rerun checks, and keep the Azure DevOps doc corrections intact.

[Copilot]

@copilot This PR is now merge-conflicted after recent merges. Please rebase/update it onto latest main, resolve the doc overlaps cleanly, rerun checks, and keep the Azure DevOps doc corrections intact...

Done in commit 2037401. The conflict was in configure-scope.md — our earlier commits had accidentally dropped Bitbucket content that was already on main (the Bitbucket example, the "What It Does (Bitbucket)" section, and the richer per-plugin descriptions for --org, --repos, and --repos-file). The fix restores all of that from main while keeping the Azure DevOps additions intact. The branch now applies cleanly on top of main with no overlapping doc regressions.