Closed CarlosCortizasCT closed 1 month ago
The latest updates on your projects. Learn more about Vercel for Git βοΈ
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
mc-app-kit-playground | β Ready (Inspect) | Visit Preview | π¬ Add feedback | Jun 19, 2024 7:48am |
merchant-center-application-kit-components-playground | β Ready (Inspect) | Visit Preview | π¬ Add feedback | Jun 19, 2024 7:48am |
Latest commit: 7f7ca8384ed5c9bcbc5764c4a6538071e9764e13
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
This PR is missing a Jira ticket reference in the title or description. Please add a Jira ticket reference to the title or description of this PR.
π₯· Code experts: no user matched threshold 10
To learn more about /:\ gitStream - Visit our Docs
Summary
Start work towards improving the Custom Applications deployment previews feature by adding a new command which will allow consumers to create/update deployments previews from the command line using our existing
mc-scripts
cli.Description
There are internal teams with some challenges that could greatly benefit of having a better non-human interaction integration with Custom Applications deployment previews. We do currently support this feature by manually adjusting some configuration in the Merchant Center UI, but it would be great if that configuration could be automatically updated from CI when a new feature-branch in created in a repository.
In order to achieve that we need to tackle different things but, as part of our X&X days, I wanted to start with this one which would allow for a logged-in user to create or update a new Custom Application deployment preview using the CLI:
(if the arguments are not provided, the command will prompt for them)
This could allow consumers to automatically trigger from their CI the creation/update of a Custom Application deployment preview for any given created branch without human intervention.
This steps still required a CLI logged-in user to run this command, but it's a first step towards the end goal.