You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+6-1
Original file line number
Diff line number
Diff line change
@@ -120,7 +120,12 @@ go install github.com/jippi/scm-engine/cmd@latest
120
120
Using scm-engine within a GitLab CI pipeline is straight forward.
121
121
122
122
1. Add a `.scm-engine.yml` file in the root of your project.
123
-
1. Create a [CI/CD Variable](https://docs.gitlab.com/ee/ci/variables/#for-a-group) named `SCM_ENGINE_TOKEN` with a value containing a [Project Access Token](https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html) with `api` scope.
123
+
1. Create a [CI/CD Variable](https://docs.gitlab.com/ee/ci/variables/#for-a-group)
124
+
1. Name must be `SCM_ENGINE_TOKEN`
125
+
1. Value must a [Project Access Token](https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html) with `api` scope.
126
+
1.`Mask`**should** be checked.
127
+
1.`Protected`**should NOT** be checked.
128
+
1.`Expand variable reference`**should NOT** be checked.
124
129
1. Setup a CI job using the `scm-engine` Docker image that will run when a pipeline is created from a Merge Request Event.
0 commit comments