-
Notifications
You must be signed in to change notification settings - Fork 116
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
New linter: warn about missing backwards migrations #270
New linter: warn about missing backwards migrations #270
Conversation
Pull Request Test Coverage Report for Build 1111
💛 - Coveralls |
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.
@brymut also rebase to the latest master which fixed the issue with failing tests in CI |
b961b4f
to
fd814a5
Compare
fd814a5
to
5bfb3db
Compare
@atodorov may I please get some help, I can't seem to be able to get the test to recognise the |
f82c3d8
to
aeac67b
Compare
pylint_django/tests/input/migrations/0003_without_backwards.txt
Outdated
Show resolved
Hide resolved
d1e011d
to
8a5a42b
Compare
8a5a42b
to
dd61a73
Compare
dd61a73
to
2b6dbd7
Compare
Refs kiwitcms/Kiwi#1774 New linter: warn about missing backwards migrations.
@atodorov, not quite sure how to handle/structure the testing for this. Should I add migrations to test with on top of the tests for the db_performance checker or should I have it with the other checkers? As it looks like the db_performance is added on separately to add the migrations path?