Check for existing db migration file #63
Merged
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
Conventional Commits Report
🚀 Conventional commits found. |
bjoernricks
force-pushed
the
check-for-sql-migration
branch
3 times, most recently
from
8c9b7ac
to
19074d7
Compare
Add a check during the release to check the existence of a corresponding sql migration script. This avoids creating defect releases.
bjoernricks
force-pushed
the
check-for-sql-migration
branch
from
19074d7
to
f012693
Compare
timopollmeier
approved these changes
Aug 8, 2023
gb-friotte
approved these changes
Aug 8, 2023
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.
What
Check for existing db migration file
Why
Add a check during the release to check the existence of a corresponding sql migration script. Don't create a defect release anymore if a sql migration script is missing.
References
Broken 22.5.0 release. Fixed with dd03aec