-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat: add skipping levels for data merging #671
feat: add skipping levels for data merging #671
Conversation
… into feature/experience-static-data-merging-strategy
…e/experience-static-data-merging-strategy
…e/experience-static-data-merging-strategy
…e/experience-static-data-merging-strategy
…e/experience-static-data-merging-strategy
…e/experience-static-data-merging-strategy
…e/experience-static-data-merging-strategy
✅ Deploy Preview for dev-composable-storefront ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for dev-oryx-components ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for dev-fulfillment ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
11 failed tests on run #1953 ↗︎
Details:
customer-note.cy.ts • 1 failed test • fa-regression
filters.cy.ts • 1 failed test • fa-regression
fully-picking-a-picklist.cy.ts • 1 failed test • fa-regression
partialy-picking-picklist.cy.ts • 1 failed test • fa-regression
picking-header-no-customer-note.cy.ts • 1 failed test • fa-regression
The first 5 failed specs are shown, see all 11 specs in Cypress Cloud. This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. |
Add skipping levels for data merging.
closes: HRZ-86533