The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: Mamaduka <[email protected]>
Co-authored-by: t-hamano <[email protected]>
Co-authored-by: adamsilverstein <[email protected]>
Co-authored-by: jeffpaul <[email protected]>
Co-authored-by: dream-encode <[email protected]>
Co-authored-by: karthick-murugan <[email protected]>
Co-authored-by: desrosj <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Size Change: +62 B (0%)

Total Size: 2.42 MB

_{compressed-size-action}

Flaky tests detected in 567cacf.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/19036878661
📝 Reported issues:

• [Flaky Test] passes the search value in the main inserter when clicking Browse all #45332 in /test/e2e/specs/editor/various/inserting-blocks.spec.js

@Mamaduka looks like some merge conflicts but once resolved probably good to merge

We might need to hold off on merging PRs related to feature enhancements that cannot be backported to the wp/6.9 branch. This is because it increases the possibility of conflicts when automatically cherry-picking bug fixes from the trunk to the wp/6.9 branch in the future. This is especially true for the Notes feature, as similar sections are frequently updated.

Great point @t-hamano, should we add a blocked label or some sort to try and prevent folks from merging non-bugs/tasks (aka enhancement) before 6.9 ships?

@Mamaduka, I've added the [Status] Blocked label, but please let me know if I've missed anything.

I'll merge this in RC cycle. Merge conflicts should be minimal then.

Rebased; going to merge after all checks are complete and green.

@Mamaduka note that we'll hopefully have some more bug fixes to merge in and backport ahead of WP 6.9 RC1 tomorrow, so not sure if a slight delay on merging this PR until after RC1 is released may be best?

Sure. I was at contributions day yesterday and remember this PR. It’s not time sensitive, will merge later.

In discussing with @desrosj @adamsilverstein perhaps the polish here may be worth getting in for 6.9 and backporting before RC1?

I rebased this branch to resolve the conflicts.

In discussing with @desrosj @adamsilverstein perhaps the polish here may be worth getting in for 6.9 and backporting before RC1?

I believe backporting is possible if there is agreement among the contributors. This PR doesn't introduce a new API, but is simply an improvement to the user experience, so I think it should be possible.

cc: 6.9 tech leads @dream-encode, @ellatrix , and @priethor for visibility.

I rebased this branch to resolve the conflicts.

In discussing with @desrosj @adamsilverstein perhaps the polish here may be worth getting in for 6.9 and backporting before RC1?

I believe backporting is possible if there is agreement among the contributors. This PR doesn't introduce a new API, but is simply an improvement to the user experience, so I think it should be possible.

cc: 6.9 tech leads @dream-encode, @ellatrix , and @priethor for visibility.

I'd like to get this in before RC1. As it's a major feature of 6.9, this could be considered a continuation task, so I see no issue with it coming in, even if it's ENH-adjacent. Would defer to my co-Tech Leads if they have any differing opinions.

The reasoning for RC1 inclusion makes sense. I've fixed the failing e2e test and this should be good to merge after all checks are green.

I just cherry-picked this PR to the wp/6.9 branch to get it included in the next release: 2835cda