-
Notifications
You must be signed in to change notification settings - Fork 146
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
@W-17900760@ Deploy Demo Storefront with SLAS Private Client #2297
base: develop
Are you sure you want to change the base?
Conversation
uses: "./.github/actions/push_to_mrt" | ||
with: | ||
CWD: "./packages/template-retail-react-app" | ||
TARGET: production |
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.
Removing this since this is redundant. We are now deploying a preset to the demo site when a new latest release tag is produced.
This does mean that we won't be deploying preview releases onto the live demo site but I can create a different step to handle this if we want.
In this slack thread, we have made a conscious decision to use RefArchGlobal as the site along with US as the default locale. To support this, additional changes were made to the zzrf-001 RefArchGlobal locales and currencies. This change is NOT reflected in |
defaultMessage: 'The React PWA Starter Store for Retail', | ||
id: 'home.title.react_starter_store' | ||
})} | ||
{{else}} |
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.
Small change here to make it more obvious in the demo site when locale is changed to another language.
This PR makes the following changes:
Testing the changes:
Demo site: https://pwa-kit.mobify-storefront.com/
Generator:
Run
node packages/pwa-kit-create-app/scripts/create-mobify-app-dev.js --preset retail-react-app-demo-private --outputDir yourOutputDir
CI:
The CI will trigger if you apply a change to this PR branch or if you publish a release that updates the latest release tag.
Here are some sample CI showing the workflow:
CI that deployed a bundle to the demo site - workflow conditions were tweaked to allow this to proceed
CI that did not deploy the demo site when triggered by something other than the latest release being published