From 068c4f17502f15a66ec126508a7095b0aa5cbb9b Mon Sep 17 00:00:00 2001
From: Muhammed-Ali Demir <muhammed.demir@ptb.de>
Date: Wed, 27 Sep 2023 14:26:09 +0000
Subject: [PATCH] Update README.md
---
README.md | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index 632207f..5bcdaa1 100644
--- a/README.md
+++ b/README.md
@@ -83,5 +83,9 @@ See [the Licence](LICENSE.md) for the specific language governing permissions an
2. Bump the version with `yarn version [major | minor | patch | ...]`,
e.g. `yarn version patch` (if the script is not installed, type `yarn plugin import version`)
3. Push all commits to the remote
-4. Create a tag with the following name: `v<version>` (e.g. `v1.0.0`) (https://www.jetbrains.com/help/webstorm/use-tags-to-mark-specific-commits.html#tag_commit)
-5. Push the tag to the remote, the CI will create a release and publish the package
+4. Create a tag with the following name: `v<version>` (e.g. `v1.0.0`)
+ a) In webstorm glick on Git-> New Tag
+ b) As the 'Tag name' type in `v<version>` (e.g. `v1.0.0`)
+ c) In the commit field type in the Commit SHA from the commit history and click on 'Validate'
+ (Source: https://www.jetbrains.com/help/webstorm/use-tags-to-mark-specific-commits.html#tag_commit)
+5. Push the tag to the remote (Click on push and set the check box saying Push tags), the CI will create a release and publish the package
--
GitLab