Migrate events #42
Closed
Migrate events #42
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
|
@DesmondSanctity there was a simpler way we migrated the events. I'll gracefully close this PR. but it was an eye opener. thanks you so much for the contribution |
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 fixes #25
how to apply the fix:
export IMPORT_EVENTS_URL="https://<live-server-address>/api/import-events"npm run migrate-eventsto trigger the bash script and wait for the magic.this solution can be better if the event is still saved to the ReadME moving forward or we can find a way to auto-save to the database whenever an event badging is completed.