bb reviewer-group¶
Create, list and change reviewer groups and their members
5 commands.
bb reviewer-group create- Create a reviewer group
bb reviewer-group delete- Delete a reviewer group
bb reviewer-group list- List reviewer groups
bb reviewer-group update- Update a reviewer group
bb reviewer-group users- List the members of a repository reviewer group who can see the repository
bb reviewer-group create¶
Create a reviewer group
bb reviewer-group create <name> [flags]
# A group of reviewers for one repository
bb reviewer-group create backend-team --repo PROJ/repo --users alice,bob
# For every repository of a project
bb reviewer-group create backend-team --project PROJ --users alice,bob \
--description "Owners of the backend services"
--description string- Description of the reviewer group
--users strings- Members by username (repeatable or comma-separated); required, because Bitbucket refuses a reviewer group with no members
Inherited from bb reviewer-group:
--project string- Project key
--repo string- Repository as PROJECT/slug
Also takes the global flags.
Dry run: Checks your permission and the current state this depends on, without changing anything (preconditions-checked)
Output with --json, where ? marks a field that can be absent
data
id? integer Group identifier, for bb reviewer-group update, delete and users.
name? string Group name.
description? string Description, when one was given.
avatarUrl? string Group avatar, when one is configured.
scope? PROJECT|REPOSITORY PROJECT when the group is defined on the project, REPOSITORY when on the
repository itself.
users? list of object Every member, whether or not they can see the repository, when the endpoint
returned them.
id? integer User identifier.
name? string Username.
displayName? string Human-readable name.
emailAddress? string Email address, when the instance exposes it.
slug? string URL-safe form of the username.
type? string Account kind: NORMAL for a person, SERVICE for an integration account.
active boolean Whether the account is enabled.
bb reviewer-group delete¶
Delete a reviewer group
bb reviewer-group delete <reviewer-group-id> [flags]
# By the id bb reviewer-group list prints
bb reviewer-group delete 4 --repo PROJ/repo
-y, --yes- Confirm without being asked; applies only when the target is named with --repo PROJECT/slug or --project
Inherited from bb reviewer-group:
--project string- Project key
--repo string- Repository as PROJECT/slug
Also takes the global flags.
Dry run: Checks your permission and the current state this depends on, without changing anything (preconditions-checked)
Output with --json, where ? marks a field that can be absent
data
status string Outcome of the command.
id string Identifier of the group that was deleted.
bb reviewer-group list¶
List reviewer groups
bb reviewer-group list
# A repository's reviewer groups and their members
bb reviewer-group list --repo PROJ/repo
# A project's
bb reviewer-group list --project PROJ
Inherited from bb reviewer-group:
--project string- Project key
--repo string- Repository as PROJECT/slug
Also takes the global flags.
Dry run: Runs as usual: this command changes nothing, so there is nothing to hold back
Output with --json, where ? marks a field that can be absent
data
reviewerGroups list of object or null Reviewer groups in scope.
id? integer Group identifier, for bb reviewer-group update, delete and users.
name? string Group name.
description? string Description, when one was given.
avatarUrl? string Group avatar, when one is configured.
scope? PROJECT|REPOSITORY PROJECT when the group is defined on the project, REPOSITORY when on the
repository itself.
users? list of object Every member, whether or not they can see the repository, when the endpoint
returned them.
id? integer User identifier.
name? string Username.
displayName? string Human-readable name.
emailAddress? string Email address, when the instance exposes it.
slug? string URL-safe form of the username.
type? string Account kind: NORMAL for a person, SERVICE for an integration account.
active boolean Whether the account is enabled.
bb reviewer-group update¶
Update a reviewer group
bb reviewer-group update <reviewer-group-id> [flags]
# Replace the members of a group
bb reviewer-group update 4 --repo PROJ/repo --users alice,bob,carol
# Rename it, keeping the members
bb reviewer-group update 4 --repo PROJ/repo --name platform-team
--description string- New description of the reviewer group
--name string- New name of the reviewer group
--users strings- Replace the members with these usernames (repeatable or comma-separated); omit to keep the current members
Inherited from bb reviewer-group:
--project string- Project key
--repo string- Repository as PROJECT/slug
Also takes the global flags.
Dry run: Checks your permission and the current state this depends on, without changing anything (preconditions-checked)
Output with --json, where ? marks a field that can be absent
data
id? integer Group identifier, for bb reviewer-group update, delete and users.
name? string Group name.
description? string Description, when one was given.
avatarUrl? string Group avatar, when one is configured.
scope? PROJECT|REPOSITORY PROJECT when the group is defined on the project, REPOSITORY when on the
repository itself.
users? list of object Every member, whether or not they can see the repository, when the endpoint
returned them.
id? integer User identifier.
name? string Username.
displayName? string Human-readable name.
emailAddress? string Email address, when the instance exposes it.
slug? string URL-safe form of the username.
type? string Account kind: NORMAL for a person, SERVICE for an integration account.
active boolean Whether the account is enabled.
bb reviewer-group users¶
List the members of a repository reviewer group who can see the repository
bb reviewer-group users <reviewer-group-id>
Bitbucket leaves out a member without access to the repository, whom it still keeps in the group. bb reviewer-group list names every member.
# The members of a group who can see the repository
bb reviewer-group users 4 --repo PROJ/repo
Inherited from bb reviewer-group:
--project string- Project key
--repo string- Repository as PROJECT/slug
Also takes the global flags.
Dry run: Runs as usual: this command changes nothing, so there is nothing to hold back
Output with --json, where ? marks a field that can be absent
data
users list of object or null The members who can see the repository.
id? integer User identifier.
name? string Username.
displayName? string Human-readable name.
emailAddress? string Email address, when the instance exposes it.
slug? string URL-safe form of the username.
type? string Account kind: NORMAL for a person, SERVICE for an integration account.
active boolean Whether the account is enabled.