-
Notifications
You must be signed in to change notification settings - Fork 800
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
Social | Add wpcom/v3/publicize/services
endpoint
#40559
Social | Add wpcom/v3/publicize/services
endpoint
#40559
Conversation
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
Interested in more tips and information?
|
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available. Follow this PR Review Process:
Still unsure? Reach out in #jetpack-developers for guidance! |
0ea90ca
to
ab66811
Compare
1986930
to
0b9b89f
Compare
53a4d87
to
b0190a0
Compare
0b9b89f
to
4eb8da1
Compare
Closing in favour of #40596 |
Extracted out of #40536
Proposed changes:
wpcom/v3/publicize/services
endpoint that can be used in every scenario the publicize module is usedOther information:
Jetpack product discussion
Does this pull request change what data or activity we track or use?
Testing instructions:
wpcom/v3/sites/<site_id>/publicize/services
wp.apiFetch
e.g. Block Editor