summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMark Pundsack <mark@pundsack.com>2016-03-16 18:04:42 +0000
committerMark Pundsack <mark@pundsack.com>2016-03-16 18:04:42 +0000
commit315d87595404a8bde78566ec51e23b167f041048 (patch)
tree74dd93a42013d8272090c2400a8d09bd7f8dc995
parent39fb836c482d653f540531215ccd60b327166651 (diff)
downloadgitlab-ce-315d87595404a8bde78566ec51e23b167f041048.tar.gz
Fix typo in README.md.
-rw-r--r--doc/ci/deployment/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/ci/deployment/README.md b/doc/ci/deployment/README.md
index ffd841ca9e7..7d91ce6710f 100644
--- a/doc/ci/deployment/README.md
+++ b/doc/ci/deployment/README.md
@@ -89,7 +89,7 @@ We also use two secure variables:
In GitLab CI 7.12 a new feature was introduced: Secure Variables.
Secure Variables can added by going to `Project > Variables > Add Variable`.
**This feature requires `gitlab-runner` with version equal or greater than 0.4.0.**
-The variables that are defined in the project settings are send along with the build script to the runner.
+The variables that are defined in the project settings are sent along with the build script to the runner.
The secure variables are stored out of the repository. Never store secrets in your projects' .gitlab-ci.yml.
It is also important that secret's value is hidden in the build log.