support for building a .phar command line utility from project sources #52
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.
Utility tools similar to codeclimate/php-test-reporter can usually be downloaded and used as a standalone .phar package. These binaries can be useful because importing the tool into your project's composer.json might unnecessarily restrict which dependencies you can use (see issue #31), plus there's the side benefit of taking pressure off Composer's package resolving process when you do a
composer update
.With that in mind I've ported the satooshi/php-coveralls box.json file into the project. These are the steps to produce one such phar:
And here is an example of how it might be used in a .travis.yml file.
If you were to accept this PR maybe you could distribute from now on a .phar file in the Releases page, just as Satooshi does with php-coveralls.
So, there's that. Have a nice day :)