-
Notifications
You must be signed in to change notification settings - Fork 22
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
Add PGCMP Workflow #698
Add PGCMP Workflow #698
Conversation
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.
Looks fine to me, I ran locally and Aerie ran successfully.
It looks like there's some failed checks though, and 1 remove before merge.
ad93742
to
cc8af12
Compare
|
cc8af12
to
7f3e48f
Compare
Ah, I misunderstood your instructions. I ran Aerie locally which I guess doesn't test this workflow. My comment above was because I saw some of the checks had failed against this branch. |
Yeah, that failing check is actually the one being added |
3f2d6dd
to
7d50ed7
Compare
198bc36
to
a16c840
Compare
a16c840
to
96e916a
Compare
96e916a
to
1da5f9c
Compare
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.
Looks great and the checks passed! 🎉
* Check both up and down migrations for equality * Add explanations for unrevertable migrations schema
1da5f9c
to
16f2bf4
Compare
Description
Added a workflow to:
pgcmp
to compare the dumps for equalitypgcmp
should at least one comparison fail.Verification
Successful running on this branch should indicate if it's working.
Future work
Potentially refine the script to only look at the changes between develop and the migration defined in the PR.