This repository was archived by the owner on Oct 1, 2021. It is now read-only.
feat: add PHAR generation on tag #30
Draft
Conversation
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
Member
|
Awesome, hope you solve the issues so the phar works 👍 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 adds a Box PHAR workflow to generate a PHAR for Drift when a new tag is pushed.
Check out https://github.com/owenvoke/drift/actions/runs/208504306 for an example.
What this does:
Issues
Probably need to get PHAR scoping working before merging, I had issues locally (see CI workflow here).This should now be working...
RectorRunnerexecutes the Rector binary, which is inside the PHAR so can't be run...Closes #21