Fix: add merge migration for contributions app#504
Merged
Conversation
Resolves conflicting leaf nodes (0033_submissionnote_data_field from submissions branch and 0040_convert_featured_images_to_cloudinary from dev) that caused App Runner deploys to roll back.
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.
Summary
0041) to resolve conflicting leaf nodes in the contributions migration graph0033_submissionnote_data_fieldwhile dev continued to0040_convert_featured_images_to_cloudinary, both branching from0032manage.py migrateto fail on App Runner startup, rolling back every deploy since the submissions mergeTest plan
ROLLBACK_SUCCEEDED)ai-review/endpoints are accessible on dev