Closed escapemanuele closed 1 day ago
https://calypso.live?image=registry.a8c.com/calypso/app:build-125213&env=jetpack |
https://calypso.live?image=registry.a8c.com/calypso/app:build-125213&env=a8c-for-agencies |
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:
Sections (~10 bytes removed 📉 [gzipped])
Legend
Generated by performance advisor bot at iscalypsofastyet.com.
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 install-plugin.sh $pluginSlug fix-site-migration-redirection
on your sandbox.
Related to https://github.com/Automattic/dotcom-forge/issues/9709#issuecomment-2488150145
Proposed Changes
Instead of redirecting the users to /start, when there is not site id or site slug, we redirect them to /home as it is done in the
site-setup
flowWhy are these changes being made?
When you remove the siteSlug/siteId in the /setup/site-setup steps, you get redirected to the primary site. However, when you remove the siteSlug/siteId in the /setup/site-migration/site-migration-identify step, you get redirected to the Domains step, and potentially create a new site if you continue the flow.
Testing Instructions