Skip to content
Snippets Groups Projects
Commit dad2a595 authored by Muhammed-Ali Demir's avatar Muhammed-Ali Demir :speech_balloon:
Browse files

Update README.md

parent 068c4f17
Branches
Tags
No related merge requests found
Pipeline #27918 passed
Stage: .pre
Stage: test
Hide whitespace changes
Inline Side-by-side
Showing
with 4 additions and 0 deletions
README.md
+ 4
− 0
View file @ dad2a595
...@@ -84,8 +84,12 @@ See [the Licence](LICENSE.md) for the specific language governing permissions an ...@@ -84,8 +84,12 @@ See [the Licence](LICENSE.md) for the specific language governing permissions an
e.g. `yarn version patch` (if the script is not installed, type `yarn plugin import version`) e.g. `yarn version patch` (if the script is not installed, type `yarn plugin import version`)
3. Push all commits to the remote 3. Push all commits to the remote
4. Create a tag with the following name: `v<version>` (e.g. `v1.0.0`) 4. Create a tag with the following name: `v<version>` (e.g. `v1.0.0`)
a) In webstorm glick on Git-> New Tag a) In webstorm glick on Git-> New Tag
b) As the 'Tag name' type in `v<version>` (e.g. `v1.0.0`) 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' 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) (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 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
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment