Bedrock - Migrate vanilla plugins to Composer #5
Conversation
This file contains 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
…cally migrates applicable plugins to Composer via WPackagist, or git-ignores them if their not available on Composer. * Updated Readme
|
Hey @adipvtl We decided against the automatic approach (instead analysing the directory and providing instructions), because there's nuances to be managed + the instructions provide a complete list - from instructing to use our standard WP install script to which specifying which plugins should be manually copied (eg. commercial plugins) vs composer installed. |
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.
Added a script that cans the Bedrock plugins directory and automatically migrates applicable plugins to Composer via WPackagist, or git-ignores them if their not available on Composer.
Updated Readme