Publish gl-sdk on npm registry (from local branch)#671
Merged
Conversation
ShahanaFarooqui
force-pushed
the
gl-sdk-npm-publishing
branch
5 times, most recently
from
4ef7882 to
4c59aaa
Compare
Collaborator
Author
|
Published @greenlightcln/glsdk@0.0.1 with workflow 22158240201 |
ShahanaFarooqui
force-pushed
the
gl-sdk-npm-publishing
branch
from
4c59aaa to
ec6f9b6
Compare
Collaborator
|
Very good work @ShahanaFarooqui, this is excellent! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR tests the full roundtrip of the library publishing workflow. The previous PR failed because GitHub blocks secrets on pull requests from forks, so
NPM_TOKENwas never accessible to the workflow. This PR is opened from a branch in the main repository instead, which allows secrets to be passed correctly.