-
Notifications
You must be signed in to change notification settings - Fork 794
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
Actions: Auto-labeling, testing changes to a module #18725
Conversation
Caution: This PR has changes that must be merged to WordPress.com |
This is an automated check which relies on |
bbfc8ef
to
fb5b04b
Compare
The authorize webhook is used as a fallback action for Calypso authorization flow. This PR is moving the webhook from Jetpack to `jetpack-connection`, making it available for plugins that use the package.
* Deprecate jetpack_json_wrap and migrate functionality into Sync/Functions for usage. * removal of errant comment * typo
Co-authored-by: Grant Kinney <hi@grant.mk>
…e method (#18540) * added new bridge method to sync block replacement mediaFilesBlockReplaceSync * added es-lint skip line directive
Co-authored-by: Glen Davies <glen.davies@a8c.com> Co-authored-by: Jeremy Herve <jeremy@jeremy.hu>
The general idea here is that each project should define composer commands for the different types of tests we support, and the infrastructure should just run them without doing too much that's specific to any one plugin. Thus, the PHP, JS, and Coverage workflows are rewritten to move all the Jetpack-specific stuff into Jetpack, and as a side effect the packages also get some changes to be more flexible than they had been previously. I also added some logic to better avoid running unnecessary tests: A change that only touches the Beta plugin, for example, probably doesn't need Jetpack's tests run. But a change that touches the Autoloader package will also need Jetpack tests to ensure that it didn't break Jetpack. I punted for now on the E2E tests. They're done in their own weirdly complicated way so it'll take more work to figure out which parts can be made generic, which are Jetpack-specific, and which if any we might be able to get rid of entirely.
- The new package - JS building configuration - Handy yarn commands - The WP admin menu link The new commands (run from `packages/connection-ui/` directory): - `yarn build` - `yarn watch` The Jetpack command `yarn build-packages` was also edited to also build the Connection UI package.
…ack versions (#18662) Co-authored-by: Brandon Kraft <public@brandonkraft.com>
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Co-authored-by: Jeremy Herve <jeremy@jeremy.hu>
Do not merge, just check the labels applied to this PR.