chore(migrations): normalize autodetected MetaData index name - #3177
Open
FrankApiyo wants to merge 1 commit into
Open
chore(migrations): normalize autodetected MetaData index name#3177FrankApiyo wants to merge 1 commit into
FrankApiyo wants to merge 1 commit into
Conversation
Pre-existing drift on main; surfaced by any makemigrations run. Split out of #3155 so the feature migration only creates PendingEmailChange.
2 tasks
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Changes / Features implemented
Normalizes an autodetected
MetaDataindex name. There is pre-existing drift between the models state and the migrations state onmain, so everymakemigrationsrun keeps regenerating this rename until it lands.Steps taken to verify this change does what is intended
RenameIndexoperation is generated verbatim bymakemigrationson main; CI runs migrationsSide effects of implementing this change
Before submitting this PR for review, please make sure you have: