Feature/block 178 dfuse cannot produce json data for migration #4
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
ab-ultra
force-pushed
the
feature/BLOCK-178-dfuse-cannot-produce-json-data-for-migration
branch
from
3cecf78
to
67ff39e
Compare
Duncan-Ultra
requested changes
Apr 5, 2022
ab-ultra
force-pushed
the
feature/BLOCK-178-dfuse-cannot-produce-json-data-for-migration
branch
from
67ff39e
to
c6fb7a4
Compare
Duncan-Ultra
approved these changes
Apr 5, 2022
Duncan-Ultra
deleted the
feature/BLOCK-178-dfuse-cannot-produce-json-data-for-migration
branch
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.
Adding support for binary_extension of optional for data export