-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added migration manual versioned ordering #13
Conversation
README.md
Outdated
} | ||
] | ||
``` | ||
If Baton is executed, migrations would be ordered in which they are specified (migration_1, migration_2, migration_3, migration_4) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re-wording suggestion:
If Baton is executed on an ordered migration json, then migrations would be processed in the order in which they were specified (migration_1, migration_2, migration_3, migration_4)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
README.md
Outdated
} | ||
] | ||
``` | ||
If Baton is executed, migrations would be ordered by ascending version number (migration_3, migration_2, migration_1, migration_4) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re-wording suggestion:
If Baton is executed on a versioned migration json, then migrations would be processed by the version number in ascending order (migration_3, migration_2, migration_1, migration_4)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
313690e
to
10f1149
Compare
10f1149
to
a5b4b5b
Compare
No description provided.