Allow publishing migrations separately #249
Merged
Conversation
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
|
Made a couple of minor changes, let me know what you think. |
|
Changes look good to me. Thanks! |
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.
I'm building a new
php please install:eloquent-drivercommand into Statamic Core, which will make the process of moving "things" to the Eloquent Driver much easier.The command will install the package & let you configure which repositories you want to move over.
As part of these changes, I didn't want to force users to publish all of the Eloquent Driver's migrations, even if they're only planning on switching one of two of the repositories.
This PR makes that possible by splitting the migrations into separate publish tags, grouped by repository.