[IMPORT] Migration script for transition from IMPORT V2 to IMPORT V3 #3126
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
jacquesfize
changed the title
jacquesfize
force-pushed
the
feat/migrate-v2-v3-import
branch
from
89f9c6b
to
ed28ade
Compare
jacquesfize
force-pushed
the
feat/migrate-v2-v3-import
branch
from
8c0c01e
to
93d5c50
Compare
jacquesfize
force-pushed
the
feat/import
branch
2 times, most recently
from
58fdc22
to
fd291fc
Compare
bouttier
force-pushed
the
feat/import
branch
2 times, most recently
from
22e3600
to
3cc485f
Compare
bouttier
force-pushed
the
feat/import
branch
from
dcdde5a
to
d64cff9
Compare
46 tasks
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 propose sets of codes to help user migrate from V2 to V3 of the import module.