* Change the modal condition to check if the theme is a block theme
* Only switch to TT4 if the theme is not a block theme
* Remove unnecessary code
* Add new Intro cards when the theme is customized
* Redirect to the customizer if the active theme is a classic one
* Update the "Start designing" link depending on the type of theme
* Fix lint errors
* Fix more lint errors
* Fix tests
* Remove only
* Add tests for the customize button
* Update copy
* Fix lint errors
* Try to fix tests
* Fix tests
* Add changefile(s) from automation for the following project(s): woocommerce
* Remove commented out css code
* Fix tests
* Remove unused
* Add margin to the cards
* Change active theme has mods by customize task completed
* Add events to the new intro page
* Fix color palette tests
* Remove unused 'fetchActiveThemeHasMods' function
This fixes the "select( 'core' ).getCurrentThemeGlobalStylesRevisions() is deprecated since version 6.5.0" warning
* Revert allowing any block theme in the assembler
* Prevent other block themes to go to the assembler
* Fix linting errors, restore test
* Remove only from test
Co-authored-by: Luigi Teschio <gigitux@gmail.com>
* Fix lint error
---------
Co-authored-by: github-actions <github-actions@github.com>
Co-authored-by: Luigi Teschio <gigitux@gmail.com>
* Add flaky test reporting and issue creation for Blocks
This commit introduces the functionality for identifying and reporting flaky tests within our CI workflow.
- The reporter captures flaky test results and saves them to `flaky-tests` directory.
- If a test fails initially but passes upon retries, it is marked as flaky and a corresponding report is generated.
- The workflow creates GitHub issues for flaky tests, aiding in better visibility and tracking of these intermittent issues.
1. **Workflow Changes**:
- **Archive flaky test reports**: Adds a step to archive flaky test reports generated during the test runs.
- **Merge flaky test reports**: Introduces a new step to merge all flaky test reports from different shards.
- **Create GitHub issues for flaky tests**: Implements a job that uses the `@wordpress/report-flaky-tests` package to create GitHub issues for detected flaky tests when a PR is not in draft state and flaky test reports are present.
2. **New Flaky Test Reporter**:
- Adds `flaky-tests-reporter.ts` that defines a custom Playwright reporter for identifying and recording flaky tests.
3. **Playwright Configuration**:
- Updates `playwright.config.ts` to include the new flaky tests reporter in the list of reporters when running in CI.
4. **Demo Tests**:
- Adds `demo.spec.ts` containing sample tests to validate the flaky test reporting functionality.
Implementing this feature will help us track and address flaky tests more efficiently, ensuring more stable and reliable test suites.
* Remove draft condition for testing
* 'Merge failures artifacts' job shouldn't touch flaky test artifacts
* Try fixing if condition
* Add required permissions
* Let's try providing all the permissions
* Let's try providing all the permissions
* Create flaky tests issues when PR is merged with trunk
* Update if condition
* Run action for specific paths only
* Add changefile(s) from automation for the following project(s): woocommerce-blocks
* Remove Demo file
* Remove Demo file
* Use commit hash to use exact version of the script
* Replace label with team: Kirigami & Origami
---------
Co-authored-by: github-actions <github-actions@github.com>
* Add the `Want more patterns` opt in message when tracking is not allowed
* Add notice for offline user
* Add new internal endpoint to fetch patterns
* Introduce a new step in the state machine to synchronously fetch patterns in the flow
* Remove unnecessary initialization
* Add new endpoint to check the patterns PTK availability
* Add `isPTKPatternsAPIAvailable` to context
* Add patterns opt in tracking message to homepage section
* Add tests
* Fix linting errors
* Add changefile(s) from automation for the following project(s): woocommerce
* Fix typo
---------
Co-authored-by: github-actions <github-actions@github.com>
* Check watchedEvent is part of the allowed eventTypes
* Add changefile(s) from automation for the following project(s): woocommerce
* Trigger custom event
---------
Co-authored-by: github-actions <github-actions@github.com>
* Add 'template_name' labels to Product post type and Product Category and Product Tag taxonomies
* Add changelog file
* Remove Single Product template name
* CYS: Ensure that toolbar appears only when the homepage sidebar is open
* Add changefile(s) from automation for the following project(s): woocommerce
* CYS: Ensure that toolbar appears only when the homepage sidebar is open
* use usequery hook instead of navigation API
---------
Co-authored-by: github-actions <github-actions@github.com>
* Fix WCPay incentive allowed promo notes logic
The WCPay promo notes need to be added to the allowed
list regardless if WCPay is installed and active.
We will respect marketplace suggestions and promo
dismissal settings.
* Added changelog entry
* focus description when generating slug
* focus the name once the modal renders
* changelog
* do not focus on description field
* isSecondary is depcreated. use "variant" prop
* move changelog file
* Deprecate pr-smoke-test.yml
* Add configs for each environment
* Add scripts
* Add arguments to playwright command
* Update pnpm scripts and existing e2e projects
* Fix shellcheck warning
* Update test env start for Gutenberg stable run
* Add changelog
* Remove unused var
* Set the USE_WP_ENV var
* Configure daily e2e jobs
* Rename some steps
* Hide individual filter blocks from the inserter
* Add changefile(s) from automation for the following project(s): woocommerce-blocks
* Adjust E2E tests to check for hidden filters
* Fix file conflict
---------
Co-authored-by: github-actions <github-actions@github.com>
Co-authored-by: roykho <roykho77@gmail.com>
Previously, we registered block categories on the client-side, leading to them not
being available until client initialization. This meant, for example, that hooking
external blocks to our categories would result in a warning.
With this change, we register the categories server-side, and only update them
on the client-side to attach the SVG icon. This is the recommended approach
in the Gutenberg docs, to make sure we use the SVG primitive, which affords some
accessibility features.
* Add a higher priority z-index to coming soon banner
* Add changefile(s) from automation for the following project(s): woocommerce
---------
Co-authored-by: github-actions <github-actions@github.com>
* Adjust border and box-shadow color for textual inputs
* WIP: Style checkboxes
* Vertically center checkmark
* Adjust focus outline width
* Adjust selected checkbox background in light mode
* Adjust background color of selected radio button
* Add chevron icon to dropdown fields
* Add changelog
* Fix CSS lint issues
* Adjust outline width
* Revert checkbox styles
* Adjust input field height and label size
* Revert box-shadow styles
* Add spacing between coupon title and coupon code
* Simplify onFocus and onBlur
* Fix outline width when focusing combobox
* Ensure chevron points down after selecting value
* Adjust outline color of focused delivery option
* POC: Use currentColor for focus states
* Revert "Add phone number to my account shipping address. (#47062)"
This reverts commit 4840af874a.
* Add changefile(s) from automation for the following project(s): woocommerce
---------
Co-authored-by: github-actions <github-actions@github.com>
* Use correct AND expression
* Add changefile(s) from automation for the following project(s): woocommerce-blocks
---------
Co-authored-by: github-actions <github-actions@github.com>
* Add To Cart Form: Improve the default style and add the Stepper style
* fix height button when no variation is selected
* not allow the user to set 0 as value of the input
* format css
* fix padding
* format css
* fix CSS
* unset margin to align with the button
* Fix coming soon footer banner doesn't display properly on tablet and mobile
* Add changelog
* Fix test
* Revert button text change
* Revert test change