summaryrefslogtreecommitdiff
path: root/doc/ci/examples/semantic-release.md
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2023-04-20 11:43:17 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2023-04-20 11:43:17 +0000
commitdfc94207fec2d84314b1a5410cface22e8b369bd (patch)
treec54022f61ced104305889a64de080998a0dc773b /doc/ci/examples/semantic-release.md
parentb874efeff674f6bf0355d5d242ecf81c6f7155df (diff)
downloadgitlab-ce-dfc94207fec2d84314b1a5410cface22e8b369bd.tar.gz
Add latest changes from gitlab-org/gitlab@15-11-stable-eev15.11.0-rc42
Diffstat (limited to 'doc/ci/examples/semantic-release.md')
-rw-r--r--doc/ci/examples/semantic-release.md15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/ci/examples/semantic-release.md b/doc/ci/examples/semantic-release.md
index 0b4b2054610..2146d76e4d6 100644
--- a/doc/ci/examples/semantic-release.md
+++ b/doc/ci/examples/semantic-release.md
@@ -168,3 +168,18 @@ Then, install the module:
```shell
npm install --save @gitlab-examples/semantic-release-npm
```
+
+## Troubleshooting
+
+### Deleted Git tags reappear
+
+A [Git tag](../../user/project/repository/tags/index.md) deleted from the repository
+can sometimes be recreated by `semantic-release` when GitLab runners use a cached
+version of the repository. If the job runs on a runner with a cached repository that
+still has the tag, `semantic-release` recreates the tag in the main repository.
+
+To avoid this behavior, you can either:
+
+- Configure the runner with [`GIT_STRATEGY: clone`](../runners/configure_runners.md#git-strategy).
+- Include the [`git fetch --prune-tags` command](https://git-scm.com/docs/git-fetch#Documentation/git-fetch.txt---prune-tags)
+ in your CI/CD script.