summaryrefslogtreecommitdiff
path: root/doc/user/project/releases
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2021-01-06 18:10:52 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2021-01-06 18:10:52 +0000
commit653048c5eeb8351344155d5e03a7d5a6138ba6ec (patch)
tree85ae41bb39070a2293c6b48fe56028da43cca51f /doc/user/project/releases
parent04a42f5e032537fc95c5158379748a7ff44385d5 (diff)
downloadgitlab-ce-653048c5eeb8351344155d5e03a7d5a6138ba6ec.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/project/releases')
-rw-r--r--doc/user/project/releases/index.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/user/project/releases/index.md b/doc/user/project/releases/index.md
index 06b614f877a..90d7ac0a3c2 100644
--- a/doc/user/project/releases/index.md
+++ b/doc/user/project/releases/index.md
@@ -200,7 +200,7 @@ If the job that's executing is within a freeze period, GitLab CI/CD creates an e
variable named `$CI_DEPLOY_FREEZE`.
To prevent the deployment job from executing, create a `rules` entry in your
-`gitlab-ci.yaml`, for example:
+`gitlab-ci.yml`, for example:
```yaml
deploy_to_production: