Fix handbook generation when Phar is used directly#476
Merged
schlessera merged 4 commits intomainfrom Dec 8, 2023
Merged
Conversation
swissspidy
reviewed
Dec 8, 2023
| WP_CLI::error( "Couldn't access md5 hash for release (HTTP code {$response->status_code})" ); | ||
| } | ||
| ``` | ||
| or in the body for POST requests. |
Member
There was a problem hiding this comment.
@schlessera Where is this coming from? 🤔 Looks a bit out of place
Member
Author
There was a problem hiding this comment.
Hmm, good catch. Looks like the parsing fails here.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In the case where the handbook generation is triggered via anything else than the
wp-cli-devenvironment, the script was broken and did not correctly recognize the$repo_url.This change fixes this to make sure packages are correctly identified from within a
vendorfolder.