Skip to content

Commit 4649afe

Browse files
authored
Merge pull request #643 from linear-b/bitbucket-integration-user-name
enforce `gitstream` in bb user name
2 parents b31914b + 7283665 commit 4649afe

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

docs/bitbucket-installation.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,7 @@ description: Install gitStream to your Bitbucket workspace.
1414
1. Bitbucket Cloud account
1515
2. Bitbucket Pipelines enabled
1616
3. <a href="https://app.linearb.io/login" target="_blank">Login</a>, or <a href="https://app.linearb.io/sign-up" target="_blank">create a free account</a> on the LinearB app, and follow the steps to connect gitStream using a Bitbucket integration.
17+
4. A dedicated user for gitStream, whose name includes the term **"gitstream"**.
1718

1819
Bitbucket Installation Overview
1920

@@ -24,9 +25,7 @@ Bitbucket Installation Overview
2425

2526
## Designate a gitStream User Account
2627

27-
gitStream automation rules are executed on behalf of the user account configured when you install the gitStream service. This account must have the necessary permissions to the relevant repositories.
28-
29-
We recommend creating a dedicated service account to easily control access to individual repositories. You can also use your professional or personal Bitbucket account for this, resulting in all automations being executed under that account.
28+
gitStream automation rules are executed by the user account configured when you authorize LinearB. A meaningful account identifier whose name contains the string `gitstream` (case insensitive), such as `gitStream-cm`, is required to ensure clarity and proper identification of the automated actions. This account must have the necessary permissions to the relevant repositories.
3029

3130
!!! tip "Use this account when you integrate gitStream"
3231
Make sure to use this account when authorizing Bitbucket in LinearB.

0 commit comments

Comments
 (0)