feat: skip-execution flag for migrate command #1563
+113
−0
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.
Pull Request check-list
Please make sure to review and check all of these items:
npm run testpass with this change (including linting)?Description of change
Skipping Migration Execution
In some cases you may want to mark migrations as completed without actually executing their SQL. This can be useful when:
- The database schema was applied manually
- You are syncing migration history between environments
- You are adopting Sequelize CLI for an existing database
- You want to avoid re-running destructive or already-applied changes
For this purpose, I have implemented a custom
--skip-executionflag.