Conversation
…t being accessible
bdalsass
approved these changes
Dec 22, 2025
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
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.
Base information
Symptom (bug)
When executing PHP coverage in PHPStorm, it can't access the result file as it is output in the PHP container.
Reproduction procedure (bug)
Cause (bug)
With PHPStorm, the XML file is output in
/opt/phpstorm-coveragein the PHP container.PHPStorm running locally can't access the result file.
Proposed solution (bug and enhancement)
Add a new volume to the Docker compose recipe to mount the PHP coverage output folder locally.
Thanks to @Lenaick for pointing this out to me!
Checklist before requesting a review
Checklist of things to do before PR is ready to merge