Updated README to use composer require instead of manual edit #5
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
Manual editing of `composer.json` is no longer needed thanks to `composer require` choosing sensible defaults. This is dependent on tagging releases in this package
|
Thanks you for your great contributions to this @grantlucas, as it seems you also care about this project, this is why I added you as a collaborator. So you can help me to improve this package and deliver value to the community. Thank you for your help ✨ |
OleMchls
added a commit
that referenced
this pull request
Feb 25, 2015
Updated README to use composer require instead of manual edit
|
@Nesquick Thanks! That was a nice surprise. Glad to help out and it helps prevent duplication of packages! |
|
yeah, sure that was the idea :) |
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.
Manual editing of
composer.jsonis no longer needed thanks tocomposer requirechoosing sensible defaults.As brought up in Issue #3, this is dependent on tagging releases in this package.
This would also take out the need of
dev-masterallowing for more reliable dependencies since changes committed to master won't automatically trigger a new release.