Bitbucket settings (bitbucket:)
bitbucket: configures one or more Bitbucket Cloud workspaces. The settings below cover connection and auth, which workspaces/repos to include or exclude, and, if you also run work-metrics, the local git-clone tuning it uses to classify commits, since Bitbucket has no blame or PR-diff API of its own.
Key
Required
Default
Description
instance_slug
Yes
-
Unique name for this instance
No
-
Atlassian account email (required for basic auth). Omit for Hivel-managed credentials
token
Yes (self-hosted)
-
Bitbucket repository access token. Omit for Hivel-managed credentials - see Hivel-managed credentials below
url
No
https://api.bitbucket.org/2.0
Override for Bitbucket Server
earliest_data_date
Yes
-
YYYY-MM-DD
include_workspaces
No
all accessible
Workspace slugs to sync
exclude_workspaces
No
-
Workspace slugs to skip
include_repos
No
all
Repo slugs to sync
exclude_repos
No
-
Repo slugs to skip
extra_branches
No
-
Additional branches to fetch
concurrent_threads
No
5
Goroutines for concurrent repo fetching
skip_ssl_verification
No
false
Disable TLS verification
exclude_commit_patterns
No
-
Glob patterns for commit messages to skip
exclude_pr_source_branches
No
-
Glob patterns for PR source branch
exclude_pr_target_branches
No
-
Glob patterns for PR target branch
exclude_file_paths
No
-
Glob patterns for file paths in PRs
redact_names_and_urls
No
false
Redact names and URLs
strip_text_content
No
false
Strip all text content
clone_cache_dir
No
/var/hivel/repo_cache
`work-metrics` only - local repo cache root; Bitbucket Cloud has no blame REST API either, 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
Last updated