diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-12-05 06:08:47 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-12-05 06:08:47 +0300 |
| commit | f0208efd0b9afee8a00690d430e9aec2171a1955 (patch) | |
| tree | 9bf10cd37233e54bcdf84dbb76d5a52aaedd56cf /doc/user/group/compliance_frameworks.md | |
| parent | f50a7f8d970c50026e52c0b5d1c444b365d3b795 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/group/compliance_frameworks.md')
| -rw-r--r-- | doc/user/group/compliance_frameworks.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/user/group/compliance_frameworks.md b/doc/user/group/compliance_frameworks.md index 8b5cf4ba935..0e976cec866 100644 --- a/doc/user/group/compliance_frameworks.md +++ b/doc/user/group/compliance_frameworks.md @@ -205,7 +205,7 @@ When creating such an MR against a project with CF pipelines, the above snippet This is because in the context of the target project, `$CI_COMMIT_REF_NAME` evaluates to a non-existing branch name. To get the correct context, use `$CI_MERGE_REQUEST_SOURCE_PROJECT_PATH` instead of `$CI_PROJECT_PATH`. -This variable is only availabe in +This variable is only available in [merge request pipelines](../../ci/pipelines/merge_request_pipelines.md). For example, for a configuration that supports both merge request pipelines originating in project forks and branch pipelines, |