Add support for django-flags source API changes #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Sep 26, 2018
willbarton
force-pushed
the
support-flag-sources
branch
from
3ec9456
to
f7dd6cc
Compare
The test matrix has been updated to test against: - The LTS Django and Wagtail versions that support Python 2.7 - The last Wagtail version to support Django 1.11 - The latest versions of Wagtail and Django
willbarton
force-pushed
the
support-flag-sources
branch
from
f7dd6cc
to
47834f5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for the changes introduced in cfpb/django-flags#12.
Travis will fail on this PR until cfpb/django-flags#12 is merged and released.