diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-01-14 06:16:05 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-01-14 06:16:05 +0300 |
commit | 4df4bbed3ee2333c23f50952d55178418eedfbe4 (patch) | |
tree | acf4669870419e64a791872f72b651260ce89a93 /doc/user/project/releases | |
parent | 0426ca208d7f3d54f5ec7572b7d5dff33a97ee87 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/project/releases')
-rw-r--r-- | doc/user/project/releases/index.md | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/doc/user/project/releases/index.md b/doc/user/project/releases/index.md index 984d44a4f3a..9e8a60ce430 100644 --- a/doc/user/project/releases/index.md +++ b/doc/user/project/releases/index.md @@ -130,7 +130,11 @@ release creation, the release job fails. #### CI/CD example of the `release` keyword To create a release when you push a Git tag, or when you add a Git tag -in the UI by going to **Repository > Tags**: +in the UI by going to **Repository > Tags**: + +NOTE: +Do not provide **Release notes** when you create the Git tag in the UI. +Providing release notes creates a release, resulting in the pipeline failing. ```yaml release_job: @@ -827,3 +831,7 @@ Make sure that the user or a service/bot account is allowed to [create the protected tag](../protected_tags.md#configuring-protected-tags) too. See [the release permissions](#release-permissions) for more information. + +### Note about storage + +Note that the feature is built on top of Git tags, so virtually no extra data is needed besides to create the release itself. Additional assets and the release evidence that is automatically generated consume storage. |