Fixes 3232: add gh action to prevent out of order migrations #505
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.
Summary
Added Github Action to check for out of order database migrations.
Testing steps
If the content in
db/migrations.latest
does not reflect the timestamp of the newest added set of migration files indb/migrations
, the job will fail. If these timestamps match or if there are no new migrations, the job will succeed.Can test by:
db/migrations.latest
. This should cause the job to fail.db/migrations.latest
content should reflect the newest added set of migration files. This should cause the job to succeed.db/migrations.latest
. This should cause the job to succeed.Checklist