@@ -18,7 +18,7 @@ To create a git tag (and therefore a release):
...
@@ -18,7 +18,7 @@ To create a git tag (and therefore a release):
1. You can add a "Message" which identifies this tag. It is only visible in the tag view, and is not necessary.
1. You can add a "Message" which identifies this tag. It is only visible in the tag view, and is not necessary.
1. Make sure you don't add any "Release notes" at this stage. The release must be created by the CI scripts, and if you enter anything in "Release notes" at this stage then the automatic creation of the release won't work.
1. Make sure you don't add any "Release notes" at this stage. The release must be created by the CI scripts, and if you enter anything in "Release notes" at this stage then the automatic creation of the release won't work.
1. Click "Create tag".
1. Click "Create tag".
1. You can see the release by going to **Project overview > Releases** after it has been created by CI (about 5 to 10 minutes). **Do not** create a release as the release will be created by the CI scripts. When the release has been created automatically, you can add any release notes you wish on the **Project overview > Releases** page.
1. You can see the release by going to **Project overview > Releases** after it has been created by CI (about 5 to **10 minutes**). **Do not** create a release by clicking on "Create release" as the release will be created by the CI scripts automatically. When the release has been created, you can add any release notes you wish on the **Project overview > Releases** page.
## Deleting old releases
## Deleting old releases
Releases can only be deleted by a maintainer or owner of the project (@Over_score in this case). GitLab will automatically delete the release entry if the corresponding tag is deleted, provided the tag is deleted by a maintainer or owner. For this reason, tags should never be deleted by a developer, only by a maintainer or owner.
Releases can only be deleted by a maintainer or owner of the project (@Over_score in this case). GitLab will automatically delete the release entry if the corresponding tag is deleted, provided the tag is deleted by a maintainer or owner. For this reason, tags should never be deleted by a developer, only by a maintainer or owner.