add dump_merger.sh script and sql needed to inserts on dump #76
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 is intended to provide a script to make it easy to create mailroom_test.dump from the nyaruka remote with whatever you need to keep in a fork, making conflict resolution easier with mailroom_test.dump.
requirements: docker, and bash
How to use:
After resolving the mailroom_test.dump conflict anyway, don't worry about the result, follow the next steps to make the dump ok.
on repository top level directory run:
now you have a dump compatible with your fork.
obs: you can only run the script without variable if need to reconcile with the dump from nyaruka main.
when creating features with tests that need records in the dump in PR that will not be opened for nyaruka, or else that do, this script will be of great help.