Skip to content

Commit 209aeaa

Browse files
authored
Update bitbucket-installation.md
1 parent a2f3351 commit 209aeaa

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/bitbucket-installation.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,16 +26,16 @@ Bitbucket Installation Overview
2626

2727
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.
2828

29-
We recommend creating a dedicated service account to control access to individual repositories easily. You can also use your professional or personal Bitbucket account for this, which would result in all automations being executed under that account.
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.
3030

3131
!!! tip "Use this account when you integrate gitStream"
3232
Make sure to use this account when authorizing Bitbucket in LinearB.
3333

3434
## Create a `cm` repo and `.cm` configuration file.
3535

36-
Create a `cm` repository in your Bitbucket workspace. This repository must reside in the same project as your target repositories. In the root directory of the default branch (usually `master` or `main`), create a `gitstream.cm` rules file to define the workflow automations. The file can have any name, but it must end with `.cm`.
36+
Create a `cm` repository in your Bitbucket workspace. This repository must reside in the same project as your target repositories. In the root directory of the default branch (usually `master` or `main`), create a `gitstream.cm` rules file to define the workflow automations. The file can have any name but must end with the `.cm` extension.
3737

38-
!!! info "Configuration files locations"
38+
!!! info "Configuration File Locations"
3939
Group-level rules require your `.cm` files to be placed in the `cm` repository's root directory.
4040
You can also define specific repo-level rules under the `.cm` folder in each of the connected repositories
4141

0 commit comments

Comments
 (0)