Fix: Improve migration error messages #6770
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
martin-rueegg
force-pushed
the
fix/module-migrations
branch
from
01c4c4f
to
0931cee
Compare
luke-
approved these changes
Dec 22, 2023
|
@martin-rueegg Thanks. Any idea why the tests are failing? |
It is just one test: installing a module with migration. I need to look into it. Not sure I manage today though. |
Thank you, absolutely no hurry. |
martin-rueegg
force-pushed
the
fix/module-migrations
branch
from
0931cee
to
d40cd67
Compare
luke-
approved these changes
Jan 19, 2024
# Conflicts: # CHANGELOG-DEV.md
auto-merge was automatically disabled
January 20, 2024 09:30
Head branch was pushed to by a user without write access
|
@luke- I tried to merge |
Now it's working. Thank you! |
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.
PR Admin
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements
developbranch, not themasterbranch if no hotfixFix #xxx[,#xxx], where "xxx" is the Github issue number)If adding a new feature, the PR's description includes:
Related
developrest#148 (comment)