Azure DevOps settings (azure:)
Azure DevOps is also a list, so multiple instances (e.g. Azure DevOps Services plus an on-prem Server) are supported side by side. The settings below cover connection and auth, whether you're pointing at cloud or on-prem (is_server), which orgs/projects/repos to include or exclude, and, if you also run work-metrics, the local git-clone tuning it uses to classify commits and PRs.
Key
Required
Default
Description
instance_slug
Yes
-
Unique name for this instance
token
Yes (self-hosted)
-
Azure DevOps Personal Access Token. Omit for Hivel-managed credentials - see Hivel-managed credentials below
url
No
https://dev.azure.com
Override - required when is_server: true (full collection URL, e.g. https://host/tfs/CollectionName)
is_server
No
false
Set for Azure DevOps Server (on-prem/TFS) instead of Azure DevOps Services (cloud)
api_version
No
7.1
Override the api-version sent on every request - older on-prem Server instances often pin 7.0
earliest_data_date
Yes
-
YYYY-MM-DD
organization
No
-
Default org for single-org PATs
include_organizations
No
all accessible
Organization names to sync - takes precedence over organization
include_projects
No
all
Project names to sync
exclude_projects
No
-
Project names to skip
include_repos
No
all
Repo names to sync
exclude_repos
No
-
Repo names to skip
extra_branches
No
-
Additional branch names to fetch for all repos
include_branches
No
-
Per-repo branch override map
concurrent_threads
No
5
Goroutines for concurrent repo fetching
skip_ssl_verification
No
false
Disable TLS verification (self-signed certs on Server)
exclude_commit_patterns
No
-
Glob patterns matched against commit messages to skip
exclude_pr_source_branches
No
-
Glob patterns for PR source branch to skip (e.g. dependabot/*)
exclude_pr_target_branches
No
-
Glob patterns for PR target branch to skip
exclude_teams
No
-
Glob patterns for team names to skip
redact_names_and_urls
No
false
Replace names and URLs with redacted-NNNN placeholders
strip_text_content
No
false
Strip all text (commit messages, PR titles, etc.)
clone_cache_dir
No
/var/hivel/repo_cache
`work-metrics` only - local repo cache root; Azure has no blame/PR-diff REST API, so classification clones instead
clone_mode
No
shallow-depth
`work-metrics` only - full, shallow-depth, or shallow-since
clone_depth
No
30
`work-metrics` only - commits to fetch when clone_mode: shallow-depth
clone_since_days
No
30
`work-metrics` only - days lookback when clone_mode: shallow-since
Azure DevOps API used: REST, api-version 7.1 by default. Both Azure DevOps Services (cloud) and Azure DevOps Server (on-prem/TFS) are supported.
Multi-instance credentials - use a different ${ENV_VAR} per entry (same pattern as GitHub above):
Last updated