Move to loading migrations using loadMigrationsFrom instead of publishing #70
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
chrispelzer
force-pushed
the
auto-migration-option
branch
2 times, most recently
from
c75e82b to
c900188
Compare
…rationsFrom` without the need to publish the migrations. Renamed the migration to work with both loadMigrationsFrom and publishing, publishing required the date/time to be part of the file to be consistent and not have new migrations, loadMigrationsFrom the date/time doesn't matter.
chrispelzer
force-pushed
the
auto-migration-option
branch
from
c900188 to
f2378cc
Compare
…ndle backwards compatibility or if migrations are not necessary for the project.
chrispelzer
force-pushed
the
auto-migration-option
branch
from
ec401b1 to
bb231da
Compare
… upgrading between versions
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.
Implement the option to have the migrations utilize Laravels
loadMigrationsFromwithout the need to publish the migrations.Renamed the migration to work with both loadMigrationsFrom and publishing, publishing required the date/time to be part of the file to be consistent and not have new migrations, loadMigrationsFrom the date/time doesn't matter.