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.
Description
When executing a command (
wp-cypress start
for example),fs.createWriteStream()
would overwrite thedebug.log
file and start afresh causing all previous output to be lost. While not inherently a problem locally, the problem starts to really show when running in CI environments where you may have multiple commands running. Due to thedebug.log
being overwritten, we would need to capture the output between each command - sometimes that's not always possible. So appending that output becomes the better option. I believe the debug should persist for as long as required or possible without being overwritten.Change Log
a
) flag to write stream.Types of changes (if applicable):
Checklist (if applicable):