You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assert a Bitbucket pull request for a git commit exists.
Synopsis
kosli assert pullrequest bitbucket [flags]
Assert a Bitbucket pull request for a git commit exists.
The command exits with non-zero exit code if no pull requests were found for the commit.
Authentication to Bitbucket can be done with an access token (recommended) or an Atlassian API token, passed via --bitbucket-username (your Atlassian account email) and --bitbucket-password.
Bitbucket app passwords are no longer supported as of 28 July 2026; replace any app passwords with API tokens. Credentials need to have read access for both repos and pull requests.
Flags
Flag
Type
Description
--bitbucket-access-token
string
Bitbucket repo/project/workspace access token. See Bitbucket access tokens for more details.
--bitbucket-password
string
Bitbucket API token. Bitbucket app passwords are no longer supported as of 28 July 2026. See Bitbucket authentication for more details.
--bitbucket-username
string
Bitbucket username (your Atlassian account email when using an API token). Only needed if you use --bitbucket-password
--bitbucket-workspace
string
Bitbucket workspace ID.
--commit
string
Git commit for which to find pull request evidence. (defaulted in some CIs: docs ). (default "HEAD")
-D, --dry-run
bool
[optional] Run in dry-run mode. When enabled, no data is sent to Kosli and the CLI exits with 0 exit code regardless of any errors.
[optional] The Kosli config file path. Config is read from this path or the default only, never implicitly from the current directory. (default "$HOME/.kosli.yml")