-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix: wrong redirect after how to migrate step #94151
Conversation
Jetpack Cloud live (direct link)
Automattic for Agencies live (direct link)
|
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: Sections (~25 bytes added 📈 [gzipped])
Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to. Legend What is parsed and gzip size?Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory. Generated by performance advisor bot at iscalypsofastyet.com. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
This PR modifies the release build for the following Calypso Apps: For info about this notification, see here: PCYsg-OT6-p2
To test WordPress.com changes, run |
Related to #94126
Proposed Changes
Redirect to the credential collection step after a user with a plan selects the DIFM option on the HOW_TO_MIGRATE step.
Why are these changes being made?
This fixes a bug on the site-migration flow. If a user with a plan selected the option DIFM on the HOW_TO_MIGRATE step they got redirected to the /migrateMessage step. This is wrong, since we should be sending users to the credential collection step.
More context: p1725373567345639/1725364409.566409-slack-C0Q664T29
Testing Instructions
/start
Pre-merge Checklist