Repository navigation
Search: Create a new search package, rename Search plugin - #21502
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 (other than "Required review") appearing at the bottom of this PR are passing or skipped. Search plugin:
|
6111fb8 to
39033dd
Compare
jeherve
left a comment
There was a problem hiding this comment.
This looks good to me. I think it would be nice to have a readme for that new package to make it clear to folks who may have been watching that package to keep up with development of the standalone plugin, but that's not a blocker, it can be done later I think.
Note: I created the new repo and Packagist entry for the new plugin location, so this should be good to merge, the package and the plugin will get pushed to the right location on merge.
|
You created the new mirror repo for the plugin, but after this is merged someone should do the work to also transfer the history from the old repo. Otherwise the new mirror will lack any history, and the new package in the old repo will weirdly reflect the history for the plugin. The "about" text and tags in the old repo could probably use updating too. Fortunately there aren't any releases or tags to figure out how to move over. |
That may be fine in this case, since not a lot has happened with
That's a good point. We can update them once this has been merged. |
|
Still probably better for the 13 commits to the plugin to be in the plugin's repo. If no one else wants to do it, poke me once this is merged and I'll take care of it. I don't mind. |
|
@anomiex: Pinging you in case you still wanted to transfer the repo history 👍 |
|
Done, history fixed in both repos. |
* master: (27 commits) Admin Page: Update upgrade buttons Tracks events (#21483) Debug Helper IDC Simulator: Add the ability to spoof the home url (#21516) Map block: Add `address` block attribute (#21412) Update wordpress monorepo (#21522) Stats Page: Add VideoPress nudge (#21513) Improve Jetpack products illustrations file size (#21514) Update dependency mediawiki/mediawiki-codesniffer to v38 (#21523) Update dependency yoast/phpunit-polyfills to v1.0.2 (#21524) Widgets: add Strava to Social Icons Widget and Social Menu (#21518) Boost: Add active modules to speed score request (#21471) Markdown: Better accessibility for Footnotes (#21495) Jetpack Plugin: Add VideoPress upgrade page (#21497) Admin Menu: moves Add new (plugin) menu item to the top for Atomic sites (#21506) General: Check the return value of get_comment() (#21080) Instagram Widget: link to user connection if user is not connected (#21512) Search: Create a new search package, rename Search plugin (#21502) Identity Crisis: Remove the unused jetpack_idc_option transient (#21492) Stats: do not update the wpcom blog details (#21441) Admin: do not display upgrade messages when on offline mode (#21444) jetpack: Catch calls to `exit()` and `die()` in PHPUnit (#21043) ...
Changes proposed in this Pull Request:
automattic/jetpack-search-plugin. This will require renaming https://github.com/Automattic/jetpack-search.automattic/jetpack-search, which will become the home of search code going forward.Jetpack product discussion
pcNPJE-oh-p2
Does this pull request change what data or activity we track or use?
No.
Testing instructions: