Add option to skip updating phpunit in modules:sync command #128
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.
Motivation
This PR introduces a optional flag
--no-phpunitsimilar to--no-phpstormfor themodules:synccommand to prevent it from modifying thephpunit.xmlfile. It is useful in scenarios where the user wants to maintain custom test suite configurations without interference from the sync process.In my case, I have configured the
app-modulesto use same test suites as the maintestsfolder.When I ran
php artisan modules:sync, the command adds the new test suiteModuleswith all the tests fromapp-modules/*/tests:Which results in warnings like this displayed in the console: