Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Migrations broken on master #315

Closed
srggrs opened this issue Sep 4, 2020 · 0 comments · Fixed by #316
Closed

Migrations broken on master #315

srggrs opened this issue Sep 4, 2020 · 0 comments · Fixed by #316
Assignees
@srggrs
Labels
bug Something isn't working

Comments

@srggrs
Copy link
Contributor

srggrs commented Sep 4, 2020 •
edited
Loading

usually ./manage.py makemigrations on the master branch should not be creating any new migration files. I realised that is not the case, and we are missing 'has_siblingsfield frommeasurements` table.

Update: that field is not really missing, only its help_text (a description of what the field is) has been updated and that's why the command create another migration file.
@srggrs srggrs self-assigned this Sep 4, 2020
@srggrs srggrs added the bug Something isn't working label Sep 4, 2020
@srggrs srggrs mentioned this issue Sep 4, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@srggrs srggrs

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix migration file 0001_initial.py askap-vast/vast-pipeline
1 participant
@srggrs