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.

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

Bump pylint django #340

Merged
merged 3 commits into from
Jul 15, 2019
Merged

Bump pylint django #340

merged 3 commits into from
Jul 15, 2019

Conversation

chocoelho
Copy link
Contributor

c/c @carlio

together with #336 it solves the reported latest pylint +pylint-django we've been facing. Tested with a running project that faced the issues reported in #335. I've created this branch from #336 so there are two commits from there in here temporarily.

@chocoelho chocoelho requested a review from carlio July 8, 2019 16:53
@coveralls
Copy link

Coverage Status

Coverage increased (+1.3%) to 78.006% when pulling 7e60eb7 on bump-pylint-django into 5a35daa on develop.

@chocoelho
Copy link
Contributor Author

Merging this in favor of having a develop PR to master.

@chocoelho chocoelho merged commit 6d97770 into develop Jul 15, 2019
@chocoelho chocoelho deleted the bump-pylint-django branch July 15, 2019 13:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants