Skip to content

Commit e674bda

Browse files
vim-zzBenLloydPearson
authored andcommitted
Update gitlab-installation.md
Remove the numbers from titles
1 parent 2fefe27 commit e674bda

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/gitlab-installation.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ GitLab Installation Overview
1717
1. Create a GitLab pipeline.
1818
1. Install the gitStream service.
1919

20-
## 1. Designate a gitStream User Account
20+
## Designate a gitStream User Account
2121

2222
gitStream automation rules are executed on behalf of the user account configured when you install the gitStream service. This account must have the `maintainer` or `owner` role to the relevant repos.
2323

@@ -26,7 +26,7 @@ We recommend creating a [dedicated service account](https://docs.gitlab.com/ee/u
2626
!!! tip "Use this account when you integrate gitStream"
2727
Make sure to use this account when authorizing GitLab in LinearB.
2828

29-
## 2. Create a `cm` repo and a CM Configuration File
29+
## Create a `cm` repo and a CM Configuration File
3030

3131
Group rules are ideal when you want to enforce 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.
3232

@@ -42,7 +42,7 @@ Create a `cm` project (repository) in your GitLab group, and create a `gitstream
4242
--8<-- "docs/downloads/gitstream.cm"
4343
```
4444

45-
## 3. Create a GitLab Pipeline
45+
## Create a GitLab Pipeline
4646

4747
Once your gitStream configuration file is set up, you need a GitLab CI configuration file to trigger gitStream automations. Create a `cm` project (repository) in your GitLab group if you haven't already. It should be created in the same group or a parent group of the target repositories. Create a `.gitlab-ci.yml` file in your new `cm` repository's default branch (usually `master` or `main`) and add the following configuration:
4848

0 commit comments

Comments
 (0)