Commit 03476ac0 authored by Rémy Coutable's avatar Rémy Coutable

Merge branch 'patch-15' into 'master'

Make clear that commits trigger CI jobs in quick start guide

See merge request !9805
parents 1df518ff f6ba5ba8
...@@ -6,7 +6,7 @@ projects. ...@@ -6,7 +6,7 @@ projects.
GitLab offers a [continuous integration][ci] service. If you GitLab offers a [continuous integration][ci] service. If you
[add a `.gitlab-ci.yml` file][yaml] to the root directory of your repository, [add a `.gitlab-ci.yml` file][yaml] to the root directory of your repository,
and configure your GitLab project to use a [Runner], then each merge request or and configure your GitLab project to use a [Runner], then each commit or
push, triggers your CI [pipeline]. push, triggers your CI [pipeline].
The `.gitlab-ci.yml` file tells the GitLab runner what to do. By default it runs The `.gitlab-ci.yml` file tells the GitLab runner what to do. By default it runs
...@@ -14,8 +14,8 @@ a pipeline with three [stages]: `build`, `test`, and `deploy`. You don't need to ...@@ -14,8 +14,8 @@ a pipeline with three [stages]: `build`, `test`, and `deploy`. You don't need to
use all three stages; stages with no jobs are simply ignored. use all three stages; stages with no jobs are simply ignored.
If everything runs OK (no non-zero return values), you'll get a nice green If everything runs OK (no non-zero return values), you'll get a nice green
checkmark associated with the pushed commit or merge request. This makes it checkmark associated with the commit. This makes it
easy to see whether a merge request caused any of the tests to fail before easy to see whether a commit caused any of the tests to fail before
you even look at the code. you even look at the code.
Most projects use GitLab's CI service to run the test suite so that Most projects use GitLab's CI service to run the test suite so that
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment