Skip to main content
Generated from bd help --doc ado. Commands for syncing issues between beads and Azure DevOps. Configuration can be set via ‘bd config’ or environment variables: ado.org / AZURE_DEVOPS_ORG - Organization name ado.project / AZURE_DEVOPS_PROJECT - Project name (single) ado.projects / AZURE_DEVOPS_PROJECTS - Project names (comma-separated) ado.pat / AZURE_DEVOPS_PAT - Personal access token ado.url / AZURE_DEVOPS_URL - Custom base URL (on-prem)

bd ado projects

List Azure DevOps projects that the configured token has access to.

bd ado pull

Pull one or more items from Azure DevOps. Accepts bead IDs or external references as positional arguments. Equivalent to: bd ado sync —pull-only —issues <refs>
Flags:

bd ado push

Push one or more beads issues to Azure DevOps. Accepts bead IDs as positional arguments. Equivalent to: bd ado sync —push-only —issues <ids>
Flags:

bd ado status

Display current Azure DevOps configuration and sync status.

bd ado sync

Synchronize issues between beads and Azure DevOps. By default, performs bidirectional sync:
  • Pulls new/updated work items from Azure DevOps to beads
  • Pushes local beads issues to Azure DevOps
Use —pull-only or —push-only to limit direction. Filters (—area-path, —iteration-path, —types, —states) restrict which work items are synced. On pull, they limit the WIQL query. On push, —types and —states filter local beads before pushing to ADO. Use —no-create with push to skip creating new ADO work items (only update existing linked items). Filters can also be persisted via config: ado.filter.area_path, ado.filter.iteration_path, ado.filter.types, ado.filter.states CLI flags override config values when both are set.
Flags: