Resolve merge conflicts between 'remove-wallet-migration-code' and 'remodel' #2571
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.
Description
This fixes merge conflicts between the
remove-wallet-migration-codeandremodelbranch.So iiuc, when
remove-wallet-migration-codeis merged intomaster(#2552), this PR—essentially mergingremove-wallet-migration-codeintoremodel—can be merged to resolve conflicts betweenremodelandmaster.Or the other way around; if this PR is merged first and then #2552, there should also be no conflicts between
remodelandmaster. 🤔But we can ofc also just merge
masterintoremodelif #2552 is merged first.Checklist
Are your changes backward compatible? Please answer below:
tbd
On a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:
tbd
For frontend changes: Tested on mobile, light and dark mode? Please answer below:
n/a
Did you introduce any new environment variables? If so, call them out explicitly here:
no
Did you use AI for this? If so, how much did it assist you?
no