fix: handle migration path conflicts for identical database declarations #836
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
davemooreuws
force-pushed
the
fix/multiple-sql-migration-declarations
branch
from
e281057 to
0100bce
Compare
davemooreuws
force-pushed
the
fix/multiple-sql-migration-declarations
branch
from
0100bce to
6bdc0f6
Compare
davemooreuws
changed the title
tjholm
previously approved these changes
Dec 22, 2024
raksiv
previously approved these changes
Dec 22, 2024
raksiv
reviewed
Dec 22, 2024
raksiv
approved these changes
Dec 22, 2024
tjholm
approved these changes
Dec 22, 2024
|
🎉 This PR is included in version 1.55.15 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
When multiple database declarations occur, check if the migrations path conficts and error with action.