diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-09-14 06:09:21 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-09-14 06:09:21 +0300 |
| commit | d5823ee1cd8ebb6fb542c10eb1eca7c7e13d05a9 (patch) | |
| tree | cedf072f2d1cd873a4a255ab177511863e4843eb /doc/ci/merge_request_pipelines | |
| parent | 368d885879821735a53401ae557acb0e1da6fb6f (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/merge_request_pipelines')
| -rw-r--r-- | doc/ci/merge_request_pipelines/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/ci/merge_request_pipelines/index.md b/doc/ci/merge_request_pipelines/index.md index 91af816a28a..3ce62936168 100644 --- a/doc/ci/merge_request_pipelines/index.md +++ b/doc/ci/merge_request_pipelines/index.md @@ -179,7 +179,7 @@ coming from a fork: Sometimes parent project members want the pipeline to run in the parent project. This could be to ensure that the post-merge pipeline passes in the parent project. -For example, a fork project could try to use a corrupted Runner that doesn't execute +For example, a fork project could try to use a corrupted runner that doesn't execute test scripts properly, but reports a passed pipeline. Reviewers in the parent project could mistakenly trust the merge request because it passed a faked pipeline. |