Task/59421 help resolving database encoding related exception when migration to v15 #17239
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
toy
force-pushed
the
task/59421-help-resolving-database-encoding-related-exception-when-migration-to-v15
branch
from
8ba8ac7 to
5922177
Compare
…atabase encoding check
Generated by 🚫 Danger |
machisuji
deleted the
task/59421-help-resolving-database-encoding-related-exception-when-migration-to-v15
branch
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.
Ticket
OP#59421
What are you trying to accomplish?
Try to warn about the database encoding problem early and add instructions on changing it.
Merge checklist