馃敡 Automate npm publish with a GitHub Action #583
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
Codecov Report
@@ Coverage Diff @@
## master #583 +/- ##
=======================================
Coverage 93.10% 93.10%
=======================================
Files 23 23
Lines 174 174
Branches 24 24
=======================================
Hits 162 162
Misses 11 11
Partials 1 1 Continue to review full report at Codecov.
|
carloscuesta
force-pushed
the
automate-npm-publish
branch
from
7403d3c
to
7132f18
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Hello! 馃憢馃徏
This PR automates the process of publishing the package to the
npmregistry. Every time that a new tagv*is pushed to the repository, automatically therelease.ymlgithub workflow will start to publish the package to the registry.Related with #577