Automatically publish the package when a GitHub release is published #1407
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
|
|
I'm fairly sure this will work, but won't know until it's used so going to merge and we'll revisit if the next release experiences problems |
keithamus
pushed a commit
that referenced
this pull request
Sep 27, 2022
…1407) * Automatically publish the gem when release happens * also yarn install * create the auth files * Use $HOME var
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.
This is based on how
octiconscurrently publishes. primer/octicons#681The
tl;dr;is that everything currently stays how it is.Previously after that last step, we would need to manually run
script/publish.This PR setups a workflow to listen for the
release: publishedevent and then prepares and then runsscript/publish