-
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
Staging Sites: Remove a filter that disables Jetpack staging mode for WPCOM staging sites #38355
Staging Sites: Remove a filter that disables Jetpack staging mode for WPCOM staging sites #38355
Conversation
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. Once your PR is ready for review, check one last time that all required checks appearing at the bottom of this PR are passing or skipped. Wpcomsh plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. |
c19794a
to
df3547f
Compare
Fixes 7894-gh-Automattic/dotcom-forge.
Proposed changes:
wpcomsh
). The hookjetpack_is_staging_site
is no longer invoked, as the only place where it was triggered is the deprecated functionis_staging_site
. The function was deprecated as part of Staging: deprecate staging logic and replace with safe mode and dev site #37023.Other information:
Jetpack product discussion
N/A
Does this pull request change what data or activity we track or use?
N/A
Testing instructions:
Note
The code is no longer used so there's no way to test it. Originally, we could test that
staging
badge was displayed. But following this change, the badge is no longer rendered.