-
Notifications
You must be signed in to change notification settings - Fork 103
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
Problem: CI does not check if migrations are consistent #797
Labels
Type: enhancement
An improvement to existing functionality.
Comments
I did something similar in fpr-admin, here: https://github.com/artefactual/archivematica-fpr-admin/blob/677607a38ed6d18bd8fa1601e1704a4096e30afe/.travis.yml#L7-L15. |
We have this working in SS: artefactual/archivematica-storage-service@b19aaa3#diff-1a8bb89e4b6a6d450e4dab3b70074e80. It could be added to the AM repo too. |
sevein
changed the title
Enhancement: automatic check for django migrations
Problem: CI does not check if migrations are consistent
Feb 28, 2019
sevein
added
triage-release-1.10
Type: enhancement
An improvement to existing functionality.
labels
Feb 28, 2019
sevein
added
the
Status: ready
The issue is sufficiently described/scoped to be picked up by a developer. Waffle label.
label
Mar 13, 2019
sevein
removed
the
Status: ready
The issue is sufficiently described/scoped to be picked up by a developer. Waffle label.
label
Dec 2, 2020
Also in AM, added in #1639. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sometimes new Pull Reqests add code that requires a django migration to be run. It would be very helpful to add a travis check for this to all PR's.
This tool might do the job:
https://github.com/rev112/django-migration-checker
The text was updated successfully, but these errors were encountered: