Change order of limitations list in environments.md
[ci skip]
This commit is contained in:
parent
6c4ba21da8
commit
21d1468c7a
1 changed files with 7 additions and 7 deletions
|
@ -489,13 +489,13 @@ fetch = +refs/environments/*:refs/remotes/origin/environments/*
|
||||||
|
|
||||||
## Limitations
|
## Limitations
|
||||||
|
|
||||||
- You are limited to use only the [CI predefined variables][variables] in the
|
1. If the branch name contains special characters (`/`), and you use the
|
||||||
`environment: name`. If you try to re-use variables defined inside `script`
|
`$CI_BUILD_REF_NAME` variable to dynamically create environments, there might
|
||||||
as part of the environment name, it will not work.
|
be complications during deployment. Follow the [issue 22849][ce-22849] for
|
||||||
- If the branch name contains special characters (`/`), and you use the
|
more information.
|
||||||
`$CI_BUILD_REF_NAME` variable to dynamically create environments, there might
|
1. You are limited to use only the [CI predefined variables][variables] in the
|
||||||
be complications during deployment. Follow the [issue 22849][ce-22849] for
|
`environment: name`. If you try to re-use variables defined inside `script`
|
||||||
more information.
|
as part of the environment name, it will not work.
|
||||||
|
|
||||||
## Further reading
|
## Further reading
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue