Added workflow to publish package on npm #18
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
This PR currently is blocked by PR #20. |
nuel77
reviewed
Nov 19, 2023
…-npm # Conflicts: # packages/numericals/package.json
nuel77
approved these changes
Nov 20, 2023
minikas
approved these changes
Nov 20, 2023
nuel77
requested changes
Nov 20, 2023
nuel77
approved these changes
Nov 22, 2023
serhii-temchenko
deleted the
feat/16/setup-ci-to-automatically-publish-on-npm
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this pull request, a new GitHub workflow has been added to publish a new package on NPM after merging or pushing changes to the
mainbranch.Closes issue #16.
To make it work -✔️ Added.NPM_AUTH_TOKENsecret should be added as a repo secret where value is an issuedpublicationtoken from NPM.