Conversation
|
Hello! 👋 Thanks for opening this pull request! Please check out our contributing guidelines. We appreciate you taking the initiative to contribute to this project. Contributing isn't limited to just code. We encourage you to contribute in the way that best fits your abilities, by writing tutorials, giving a demo at your local meetup, helping other users with their support questions, or revising our documentation. Here are some useful Composer commands to get you started:
To run a single Behat test, you can use the following command: # Run all tests in a single file
composer behat features/some-feature.feature
# Run only a specific scenario (where 123 is the line number of the "Scenario:" title)
composer behat features/some-feature.feature:123You can find a list of all available Behat steps in our handbook. |
There was a problem hiding this comment.
Code Review
This pull request updates the features/block-synced-pattern.feature file by replacing single quotes with double quotes for the --content argument in several wp block synced-pattern commands. This change is likely intended to improve cross-platform compatibility for the test suite. I have no feedback to provide.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
There was a problem hiding this comment.
Pull request overview
Updates the synced-pattern Behat feature to avoid inline --content='...' shell quoting (notably problematic on Windows) by writing block HTML to temporary files and passing those files to wp block synced-pattern commands.
Changes:
- Replace inline
--content='...'usage withAnd a *.html file:steps plus<file>positional arguments forcreate. - Update the
updatescenario to pass content via a file argument instead of--content=.... - Apply this pattern across multiple scenarios in
block-synced-pattern.featurefor consistent Windows-friendly execution.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
No description provided.