Update gitlab-installation.md #628
Conversation
PavelLinearB
commented
Dec 30, 2024
PavelLinearB
commented
![orca-security-us[bot]](https://avatars.githubusercontent.com/in/276250?s=60&v=4){kind=small}
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority | |
|---|---|---|---|
 Passed |
Secrets |  0  0  0  0 |
View in Orca |
PavelLinearB
merged commit a539b74
into
LINBEE-13204-add-cm-repo-to-doc
![fine-ai[bot]](https://avatars.githubusercontent.com/in/293841?s=60&v=4){kind=small}
|
|
||
| We recommend creating a [dedicated service account](https://docs.gitlab.com/ee/user/profile/service_accounts.html){:target="_blank"} to control access to individual repos easily. You can also use your professional or personal GitLab account for this, which would result in all automations being executed under that account, which might also affect LinearB's metrics. | ||
|
|
||
| !!! tip "Use this account when you integrate gitStream" |
There was a problem hiding this comment.
The phrase 'Group rules are ideal when you want to enforce consistent rules across every repo in your GitLab group' is repeated in the paragraph. Consider rephrasing to avoid redundancy.
Group rules are ideal for enforcing consistent rules across every repo in your GitLab group. You can define them by creating a special repository named cm in the parent group for the git repositories on which you want to run gitStream. Here, you can add automation files that apply to all repositories within that group that are connected to gitStream.
|
|
||
| ## Create a `cm` repo and a CM Configuration File | ||
| ## Create a `cm` repo and `.cm` configuration file. | ||
|
|
There was a problem hiding this comment.
The sentence 'You can name the CM file anything you want as long as it ends in .cm' is repeated. Consider removing the redundancy.
This file will contain a YAML configuration that determines the workflows that run on your organization's repos. You can name the CM file anything you want as long as it ends in .cm.
| !!! info "Configuration files go in the repo's root directory." | ||
| Group-level rules require your `.cm` files to be placed in the repository's root directory. | ||
| You can also define specific repo-level rules under the `.cm` folder in each of the connected repositories | ||
| !!! info "Configuration files locations" |
There was a problem hiding this comment.
The info box title 'Configuration files locations' is not grammatically correct. Consider changing it to 'Configuration File Locations' for better readability.
!!! info "Configuration File Locations"
1 participant
