fix php composer issue #122
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
as per php-http/discovery#213 (comment) > The right solution is to disable the plugin, you likely don't need it anyway in your CI
leohemsted
force-pushed
the
fix-build
branch
2 times, most recently
from
8af5bf8
to
e7decb3
Compare
samuelhwilliams
approved these changes
Feb 10, 2023
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.
so theres some kind of php plugin subdependency that causes issues
php-http/discovery#213
a contributor commented here:
php-http/discovery#213 (comment)
they've now tweaked composer to allow you to autodisable plugins - we might want to look in to this if this happens again?
composer/composer#11315