Emit a build artifact after github actions run #362
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
reese
force-pushed
the
reese-build-artifact
branch
from
5a2b800 to
3dcae59
Compare
reese
changed the title
fables-tales
approved these changes
Nov 20, 2022
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.
It'd be really handy to be able to test rubyfmt PRs or commits between releases on the Stripe codebase in an automated way without having to pull and build the whole repo, so this PR uploads the release binary for each OS as a build artifact, which we can fetch in some dev scripts with the
ghCLI.(N.B. I could see this being a way to make automated releases, e.g. make an action that runs on tag creation to create builds for all our supported OSs, combine the build artifacts, and publish the release)