diff options
| author | Grzegorz Bizon <grzesiek.bizon@gmail.com> | 2018-10-03 13:21:41 +0300 |
|---|---|---|
| committer | Grzegorz Bizon <grzesiek.bizon@gmail.com> | 2018-10-03 13:21:41 +0300 |
| commit | 4000358531668e07021160e436f3cdc1b873e9d7 (patch) | |
| tree | 2deef4b88577f891f378ecd227776607c80d9c38 /doc/ci/yaml | |
| parent | 09075759a428220ddfb5dacf6a6974c11956e391 (diff) | |
Few minor fixed in code and docs for only: changes
Diffstat (limited to 'doc/ci/yaml')
| -rw-r--r-- | doc/ci/yaml/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/ci/yaml/README.md b/doc/ci/yaml/README.md index ef9a00266e1..0d07b63a2dc 100644 --- a/doc/ci/yaml/README.md +++ b/doc/ci/yaml/README.md @@ -476,7 +476,7 @@ If you are pushing a **new** branch or a new tag to GitLab, only/changes is going to always evaluate to truth and GitLab will create a job. This feature is not combined with merge requests yet, and because GitLab is creating pipelines before an user can create a merge request we don't know a target branch at -this point. Without a target branchit is not possible to know what the common +this point. Without a target branch it is not possible to know what the common ancestor is, thus we always create a job in that case. This feature works best for stable branches like `master` because in that case GitLab uses previous commit, that is present in a branch, to compare against a newly pushed latest SHA. |