Registry / devops / azdo-cli

azdo-cli

JSON →
library0.8.1jsnpmunverified

The `azdo-cli` package provides a command-line interface for interacting with Azure DevOps services. It allows users to manage various Azure DevOps resources, such as work items, pull requests, and comments, directly from their terminal. The current stable version, as indicated by the latest release, is v0.9.0. The project exhibits an active development cadence, with frequent minor feature releases and dependency updates, suggesting ongoing maintenance and expansion of its capabilities. It serves as a lightweight alternative for automating Azure DevOps tasks and integrating them into scripts, potentially offering a more streamlined experience for specific use cases compared to the broader `az devops` extension for the Azure CLI, focusing on developer-centric operations.

devopsazure
Install & Compatibility
Where this runs

No compatibility data collected yet for this library.

Code
Verified usage

This quickstart demonstrates how to install `azdo-cli`, configure it with your Azure DevOps organization and a Personal Access Token (PAT), and then provides examples for listing work items, creating a new bug, and adding a comment to a pull request using the command-line interface.

# Install globally (recommended for CLI tools) npm install -g azdo-cli # Alternatively, use npx for single execution without global install # npx azdo-cli --version # Configure authentication using a Personal Access Token (PAT) # Set your Azure DevOps organization and project # Replace 'your-organization' and 'your-project' with actual values # The PAT can be set as an environment variable (AZDO_PAT) for security export AZDO_PAT="YOUR_AZURE_DEVOPS_PAT" azdo-cli config set organization "your-organization" azdo-cli config set project "your-project" # Example: List all work items in the configured project azdo-cli work-item list # Example: Create a new bug work item azdo-cli work-item create --type "Bug" --title "Broken user profile image upload" --description "Users are reporting issues when trying to upload new profile pictures after the last deployment." --assigned-to "developer@example.com" # Example: Add a comment to an existing pull request (replace 123 and repo-name) azdo-cli pr comment add --id 123 --repository "your-repo-name" --comment "Initial review complete. Looks good, minor stylistic changes suggested."
azdo --version
Debug
Known footguns
breakingThe `better-secret` feature introduced in v0.4.0 might have changed how secrets are managed or stored. Users upgrading from versions prior to v0.4.0 may need to re-configure their Personal Access Tokens (PATs) or other sensitive credentials.
gotchaPersonal Access Tokens (PATs) used for authentication must have the correct scopes enabled in Azure DevOps (e.g., 'Work Items (Read & Write)', 'Code (Read & Write)') for `azdo-cli` commands to function properly. Insufficient scopes will lead to authorization errors.
gotchaMany commands require explicit `--organization` and `--project` flags if they are not set globally via `azdo-cli config set` or through environment variables. Failure to specify these can result in 'resource not found' or 'command scope' errors.
gotchaSensitive data like Personal Access Tokens (PATs) should ideally be managed via environment variables (e.g., `AZDO_PAT`) rather than storing them directly in shell history or less secure configuration files, especially in shared environments.
Upgrade
Version history

Breaking-change detection hasn't run for this library yet.

Audit
Security & dependencies

CVE tracking and dependency tree are planned for a later release.

Agent activity
16 hits · last 30 days
bytedance
4
gptbot
3
ahrefsbot
3
amazonbot
3
dotbot
1
script
1
Resources