Forms: Add granular block categories to form editor #46626

enejb · 2026-01-15T19:50:16Z

Proposed changes:

Add granular block categories (Input, Contact, Choice, Other) specifically for the Jetpack Form editor
Each form field block now defines its formEditorCategory property to specify which category it belongs to in the form editor
Categories are dynamically registered when entering the form editor and removed when leaving
Block category overrides are applied only in the form editor context, keeping the original contact-form category for the regular post/page editor
Add missing field blocks to the allowed blocks list: field-hidden, field-time, field-slider, field-image-select
Fix incorrect block name field-file-upload → field-file
Add missing supporting blocks: dropzone, input-range, input-rating, fieldset-image-options, input-image-option

Before:

After:

Block categorization:

Category	Blocks
Basic	number, field-text, field-textarea, field-date, field-time,
Contact	field-name, field-email, field-telephone, field-url
Choice	field-checkbox, field-select, field-radio, field-checkbox-multiple, field-image-select
Advanced	field-consent, field-hidden, field-file, field-rating, field-slider

Other information:

Have you written new tests for your changes, if applicable?
Have you checked the E2E test CI results, and verified that your changes do not break them?
Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

no

Does this pull request change what data or activity we track or use?

no

Testing instructions:

Enable the central-form-management feature flag if not already enabled

add_filter( 'jetpack_block_editor_feature_flags', 'eb_register_feature' );

function eb_register_feature( $flags ) {
   $flags['central-form-management'] = true;
   return $flags;
}

Go to Forms > Add New to create a new form (or navigate to /wp-admin/post-new.php?post_type=jetpack_form)
Open the block inserter (click the + button or press /)
Verify that form field blocks are organized into four categories:
- Input: Text input field, Multi-line text field, Number input field, Hidden field
- Contact: Name field, Email field, Phone number field, Website field
- Choice: Checkbox, Dropdown, Single choice, Multiple choice, Terms consent, Rating, Image Select
- Other: Date picker, Time input, File upload, Slider
Add blocks from each category to verify they work correctly
Navigate to a regular post or page editor
Add a Form block and verify the form fields are all grouped under the single "Forms" category (not the granular categories)
Return to the form editor and verify the granular categories are still displayed

Visit the form editor by going to

github-actions · 2026-01-15T19:51:41Z

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack), and enable the update/jetpack-form-editor-add-categories branch.
To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack update/jetpack-form-editor-add-categories

Interested in more tips and information?

In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
Read more about our development workflow here: PCYsg-eg0-p2
Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

github-actions · 2026-01-15T19:51:49Z

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

✅ Include a description of your PR changes.
✅ Add a "[Status]" label (In Progress, Needs Review, ...).
✅ Add testing instructions.
✅ Specify whether this PR includes any changes to data or privacy.
✅ Add changelog entries to affected projects

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 🤖

Follow this PR Review Process:

Ensure all required checks appearing at the bottom of this PR are passing.
Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
You can use GitHub's Reviewers functionality to request a review.
When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

Copilot

Pull request overview

This PR adds granular block categories to the Jetpack Form editor to improve organization of form field blocks in the block inserter. Instead of a single "Forms" category, form fields are now organized into four categories: Input, Contact, Choice, and Other.

Changes:

Added dynamic block category registration/unregistration for the form editor context
Implemented block category override system using WordPress hooks to remap blocks to granular categories
Updated all form field blocks with formEditorCategory property
Fixed missing and incorrect block names in allowed blocks list

Reviewed changes

Copilot reviewed 25 out of 25 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
projects/packages/forms/src/form-editor/utils/form-categories.ts	New file defining the four granular categories and mapping logic
projects/packages/forms/src/form-editor/utils/block-category-override.ts	New file implementing dynamic block category override system
projects/packages/forms/src/form-editor/utils/category-utils.ts	Added functions to register/unregister form categories
projects/packages/forms/src/form-editor/index.tsx	Integrated category setup/restoration logic into form editor lifecycle
projects/packages/forms/src/form-editor/class-form-editor.php	Fixed incorrect block name and added missing field/supporting blocks to allowed list
projects/packages/forms/src/blocks/field-*.js	Added `formEditorCategory` property to each form field block definition
projects/packages/forms/changelog/update-jetpack-form-editor-add-categories	Changelog entry for the feature

Comments suppressed due to low confidence (2)

projects/packages/forms/src/form-editor/utils/form-categories.ts:1

The JSDoc example in the @param and @return descriptions is inconsistent with the actual implementation. The example uses 'text' as input and 'form-text' as output, but according to the CATEGORY_SLUG_MAP, 'text' is not a valid key. The example should use 'input' → 'form-input' instead to match the actual mapping.

/**

projects/packages/forms/changelog/update-jetpack-form-editor-add-categories:4

The changelog entry should not include the package name prefix "Form Editor" at the end since this is within the forms package changelog. Additionally, the entry should be shorter and use imperative mood. Consider: "Add granular block categories (Input, Contact, Choice, Other) to improve form field organization in the block inserter."

Added granular block categories (Input, Contact, Choice, Other) for better organization of form fields in the block inserter on the Form Editor.

projects/packages/forms/src/form-editor/utils/category-utils.ts

projects/packages/forms/src/form-editor/index.tsx

projects/packages/forms/src/form-editor/utils/category-utils.ts

projects/packages/forms/src/form-editor/utils/block-category-override.ts

jp-launch-control · 2026-01-15T20:01:46Z

Code Coverage Summary

Cannot generate coverage summary while tests are failing. 🤐

Please fix the tests, or re-run the Code coverage job if it was something being flaky.

Full summary · PHP report · JS report

Copilot

Pull request overview

Copilot reviewed 25 out of 25 changed files in this pull request and generated 4 comments.

projects/packages/forms/src/form-editor/utils/form-categories.ts

Copilot · 2026-01-15T22:16:03Z

projects/packages/forms/src/form-editor/utils/block-category-override.ts

+					originalBlockCategories.set( blockType.name, blockType.category );
+				}
+				// Update the block type's category
+				blockType.category = formCategorySlug;


Directly mutating the blockType.category property could cause issues since you're modifying objects returned from the data store. While this may work, it's generally better practice to use the appropriate dispatch methods if available. Consider checking if there's a proper API for updating block type properties, or document why direct mutation is necessary here.

projects/packages/forms/src/form-editor/utils/block-category-override.ts

projects/packages/forms/changelog/update-jetpack-form-editor-add-categories

Copilot

Pull request overview

Copilot reviewed 26 out of 26 changed files in this pull request and generated 2 comments.

projects/packages/forms/src/form-editor/utils/test/category-utils.test.ts

Copilot · 2026-01-15T22:24:24Z

projects/packages/forms/src/form-editor/index.tsx

+ * 2. Activates block category overrides to move blocks to the new categories
+ * 3. Moves the contact-form category to the front (as a fallback for non-field blocks)
+ *
+ * @return {unknown[]} previous categories array for restoration


The return type annotation uses JSDoc-style comment in a TypeScript file. Consider using TypeScript's type annotation directly in the function signature instead, or at minimum update the JSDoc syntax to match TypeScript conventions (e.g., '@returns' instead of '@return').

ilonagl · 2026-01-16T11:21:40Z

Yay, very nice!! Thanks for doing this, @enejb!

simison · 2026-01-16T11:54:52Z

Nice! This is really starting to take a form builder shape.

Here's a set of suggestions for categories and which fields to have in them. All open to feedback of course.

Category	Fields
Basic	Text, Textarea, Number, Date, Time
Contact info	Name, First name, Last name, Email, Phone number, Website
Choice	Checkbox, Dropdown, Single choice, Multiple choice, Image select
Advanced	File upload, Slider, Stars rating, Hearts rating, Hidden, Terms Consent

Reasoning:

Input → "Basic", "Standard", or "Common" could be a more descriptive fit here? — everything is "input" or "field".
Contact → rename to Contact info: feels like this would translate better in different languages without ambiguity. "Contact" also works, but we need to make sure nobody translates it as a noun or verb.
Hidden field → Move to Other category: it's a fairly esoteric field, so having it at the top in the "common" category felt off.
Date/time → Feels basic/common enough to justify top placement rather than "other" bucket way down.
Terms Concent → while it's a "choice" it's more specialized than that, so advanced made sense to me.
Stars/Hearts rating → same as above; this one is more similar to slider or number semantically than to radios/checkboxes.

ilonagl · 2026-01-16T12:55:31Z

As a rule of thumb, I’ve been following Typeform’s grouping, as users are likely familiar with it and Typeform has done extensive research to validate it.

and my initial recommendation:

@simison I agree with your proposal, here are some notes:

Hidden field → Move to Other category: it's a fairly esoteric field, so having it at the top in the "common" category felt off.

Agreed, had a similar thought.

Contact → rename to Contact info

+1.

Input → "Basic", "Standard", or "Common"

Maybe even "Recommended" or "Most common" would work here?

Basic: Text, Textarea, Number, Date, Time

The time is not fully there UX-wise (we don't have a great ability to select and only input time), so I wonder if it should be this high up?

Separate note:

Name, First name, Last name

The fact that we have three different inputs for very similar purposes seems a bit off for me. Are they supposed to be variations or separate inputs?

simison · 2026-01-16T13:22:53Z

Maybe even "Recommended" or "Most common" would work here?

Yep 👍 Common can be hard to translate since it has multiple meanings, so we'll need to be mindful what context to provide to translators so they get it right. Leaning towards "common" over "recommended" for a more neutral feeling.

The fact that we have three different inputs for very similar purposes seems a bit off for me. Are they supposed to be variations or separate inputs?

Yep, they're all variations of Name field but Gutenberg surfaces them all separately in the block picker. Same with Hearts/Stars rating. Helps with search, but adds a bit of noise in a list like this. Not a biggie, methinks. Semantically, they carry a clearly separate meaning for integrations and for form autofilling, so they're important to have.

The time is not fully there UX-wise (we don't have a great ability to select and only input time), so I wonder if it should be this high up?

I agree UX can/should be improved, but feels odd to have time & date far apart in different locations? At the end, it's just simple numbers that users can just enter, so selection doesn't feel that critical for UX. Time doesn't seem as common need as date for sure, but just seems sensible to keep them close together. I'm fine keeping them both in other/advanced category as well.

simison · 2026-01-16T13:25:46Z

projects/packages/forms/src/blocks/field-checkbox/index.js

 const name = 'field-checkbox';
 const settings = {
 	...defaultSettings,
+	formEditorCategory: 'choice',


I'm a bit concerned about including this in settings since it isn't part of block schema. Is there another way to provide remapping?

I like that it's in the same file as the block so could be something we just export as constant from here?

I tried implementing this in a different way but we always end up under a different place.

I think support make more sense and this will become even more extensible if we implement other feature this way. Since we already prefix them with the custom post type.

What I'm worried that settings has a very specific schema in Gutenberg, and adding custom elements can break or start throwing warnings in future in surprising ways.

It's already better; it's now prefixed with jetpack_, so there's no chance of confusion.

Did you look if export default { name, settings, jetpackCptCategory }; would work?

simison · 2026-01-16T13:27:31Z

projects/packages/forms/src/form-editor/utils/form-categories.ts

+	input: 'form-input',
+	contact: 'form-contact',
+	choice: 'form-choice',
+	other: 'form-other',


Should we prefix with jetpack just case like we do with our other categories elsewhere?

I don't think we need to. Since we currently don't prefix any category names like this. As far as I can tell.

Copilot

Pull request overview

Copilot reviewed 26 out of 26 changed files in this pull request and generated 1 comment.

projects/packages/forms/changelog/update-jetpack-form-editor-add-categories

edanzer

This tests largely as expected. Note: categories in the code are different than the PR description. The ones in the code are the right ones (see list below).

Create new form post, open block inserter, and confirm blocks are in new categories
Basic category contains: Text, Number, Multiline, Date, Time
Contact category contains: Name, First Name, Last Name, Email, Phone, Website
Choice category contains: Checkbox, Dropdown, Single choice, Multiple choice, Image Select
Other category contains: Consent, Hidden, Ratings, File, Slider
Add blocks to verify they work correctly
Go to normal page/post, insert form block, and confirm fields are all under usual Forms category.
Return to the form editor and verify the granular categories are still displayed

I added a few questions.

General feedback. My single biggest question/concern though is this: It's not clear to me that dividing the form fields into these categories makes it any easier to find specific fields I want. Without this PR, we do not have that many fields, and it's easy to scan a single Form category. With this PR, the way fields are divided into categories seems a bit arbitrary. It's not obvious what category I should look for to find a specific field. And I wonder if people will just have to kind of scan all the categories to find a field, rather than a single more condense Form category. cc @ilonagl @simison too.

I should add - I don't think it's a huge concern either way. So I'm ok rolling with this too. But I do wonder if we add a lot of complexity for not that much user benefit.

Introduces granular categories (input, contact, choice, other) for form field blocks in the Jetpack Form editor. Adds a `formEditorCategory` property to each field block and utilities to register/unregister these categories and override block categories dynamically. Updates the form editor logic to use these new categories, improving block organization and user experience.

Introduces unit tests for registerFormCategories and unregisterFormCategories to verify correct category insertion, removal, immutability, and reversibility.

Co-authored-by: Copilot <[email protected]>

Simplifies the logic for overriding block categories in the form editor by using a filter and the reapplyBlockTypeFilters dispatch action. Removes manual tracking and restoration of original categories, and introduces an activation flag to control when overrides are applied. This improves maintainability and ensures categories are updated consistently.

Category assignments: - Basic: Text, Textarea, Number, Date, Time - Contact info: Name, Email, Phone number, Website - Choice: Checkbox, Dropdown, Single choice, Multiple choice, Image select - Advanced: File upload, Slider, Rating, Hidden, Terms Consent

Copilot

Pull request overview

Copilot reviewed 32 out of 32 changed files in this pull request and generated 5 comments.

Comments suppressed due to low confidence (1)

projects/packages/forms/tests/php/form-editor/Form_Editor_Test.php:424

The test's expected supporting blocks list is missing the newly added supporting blocks: 'jetpack/dropzone', 'jetpack/input-range', 'jetpack/input-rating', 'jetpack/fieldset-image-options', and 'jetpack/input-image-option'. These blocks were added to the allowed list in the PHP code but are not verified by this test. Add these blocks to the expected_supporting_blocks array to ensure the test validates the complete allowed blocks list.

projects/packages/forms/changelog/update-jetpack-form-editor-add-categories

Copilot

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

Copilot

Pull request overview

Copilot reviewed 32 out of 32 changed files in this pull request and generated 22 comments.

Comments suppressed due to low confidence (1)

projects/packages/forms/tests/php/form-editor/Form_Editor_Test.php:465

The test_allowed_blocks_list_completeness test is missing the newly added field blocks (field-hidden, field-time, field-slider, field-image-select) and supporting blocks (dropzone, input-range, input-rating, fieldset-image-options, input-image-option). These should be added to the expected blocks arrays to ensure comprehensive test coverage of the allowed blocks list.

Copilot · 2026-01-21T12:56:52Z

projects/packages/forms/src/blocks/field-image-select/index.tsx

+	supports: {
+		...defaultSettings.supports,
+	},


The supports object is redundantly spreading defaultSettings.supports without adding any new properties. Since no additional support properties are being added, this spread operation is unnecessary. Consider removing this redundant code or only include it if additional properties need to be added.

Suggested change

supports: {

...defaultSettings.supports,

},

Copilot · 2026-01-21T12:56:52Z

projects/packages/forms/src/blocks/field-date/index.js

+export const name = 'field-date';
+
+export const form_editor = {
+	category: 'advanced',


The field-date block is categorized as 'advanced' but according to the PR description, it should be in the 'Basic' category. The PR description table states: "Basic: number, field-text, field-textarea, field-date, field-time". Please update the category to 'basic' to match the intended design.

Suggested change

category: 'advanced',

category: 'basic',

Copilot · 2026-01-21T12:56:53Z

projects/packages/forms/src/blocks/field-time/index.js

+export const name = 'field-time';
+
+export const form_editor = {
+	category: 'advanced',


The field-time block is categorized as 'advanced' but according to the PR description, it should be in the 'Basic' category. The PR description table states: "Basic: number, field-text, field-textarea, field-date, field-time". Please update the category to 'basic' to match the intended design.

Suggested change

category: 'advanced',

category: 'basic',

Copilot · 2026-01-21T12:56:53Z

projects/packages/forms/src/blocks/field-textarea/index.js

+	supports: {
+		...defaultSettings.supports,
+	},


The supports object is redundantly spreading defaultSettings.supports without adding any new properties. Since no additional support properties are being added, this spread operation is unnecessary. Consider removing this redundant code or only include it if additional properties need to be added.

Suggested change

supports: {

...defaultSettings.supports,

},

Copilot · 2026-01-21T12:56:53Z

projects/packages/forms/src/blocks/field-number/index.js

+	supports: {
+		...defaultSettings.supports,
+	},


The supports object is redundantly spreading defaultSettings.supports without adding any new properties. Since no additional support properties are being added, this spread operation is unnecessary. Consider removing this redundant code or only include it if additional properties need to be added.

Copilot · 2026-01-21T12:56:57Z

projects/packages/forms/src/blocks/field-consent/index.js

+	supports: {
+		...defaultSettings.supports,
+	},


The supports object is redundantly spreading defaultSettings.supports without adding any new properties. Since no additional support properties are being added, this spread operation is unnecessary. Consider removing this redundant code or only include it if additional properties need to be added.

Suggested change

supports: {

...defaultSettings.supports,

},

Copilot · 2026-01-21T12:56:57Z

projects/packages/forms/src/blocks/field-checkbox/index.js

+	supports: {
+		...defaultSettings.supports,
+	},


The supports object is redundantly spreading defaultSettings.supports without adding any new properties. Since no additional support properties are being added, this spread operation is unnecessary. Consider removing this redundant code or only include it if additional properties need to be added.

Suggested change

supports: {

...defaultSettings.supports,

},

Copilot · 2026-01-21T12:56:58Z

projects/packages/forms/changelog/update-jetpack-form-editor-add-categories

+Significance: minor
+Type: added
+
+Added granular block categories for better organization of form fields in the block inserter on the Form Editor.


The changelog entry should use imperative mood. Change "Added" to "Add" to follow the project's changelog guidelines.

Copilot · 2026-01-21T12:56:58Z

projects/packages/forms/src/form-editor/utils/block-category-override.ts

+/**
+ * Filter callback that overrides block categories for form field blocks.
+ *
+ * This reads the category from supports.jetpack_form.category and maps


The JSDoc comment incorrectly states "reads the category from supports.jetpack_form.category" but the implementation actually reads from form_editor.category on the childBlock object. Update the documentation to accurately reflect the implementation.

Suggested change

* This reads the category from supports.jetpack_form.category and maps

* This reads the category from each child block's `form_editor.category` field and maps

Copilot · 2026-01-21T12:56:58Z

projects/packages/forms/src/form-editor/utils/form-categories.ts

+/**
+ * Map of short category names to full category slugs.
+ *
+ * Blocks define their category in supports.jetpack_form.category using the short name


The JSDoc comment incorrectly states "Blocks define their category in supports.jetpack_form.category" but blocks actually define it in the form_editor.category property. Update the documentation to accurately reflect the implementation.

Suggested change

* Blocks define their category in supports.jetpack_form.category using the short name

* Blocks define their category in form_editor.category using the short name

Copilot AI review requested due to automatic review settings January 15, 2026 19:50

Copilot started reviewing on behalf of enejb January 15, 2026 19:50 View session

github-actions bot added [Block] Contact Form Form block (also see Contact Form label) [Feature] Contact Form [Package] Forms labels Jan 15, 2026

github-actions bot added the [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. label Jan 15, 2026

Copilot AI reviewed Jan 15, 2026

View reviewed changes

enejb added [Status] Needs Review This PR is ready for review. and removed [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. labels Jan 15, 2026

Copilot AI review requested due to automatic review settings January 15, 2026 22:11

Copilot started reviewing on behalf of enejb January 15, 2026 22:12 View session

Copilot AI reviewed Jan 15, 2026

View reviewed changes

github-actions bot added the [Tests] Includes Tests label Jan 15, 2026

Copilot AI review requested due to automatic review settings January 15, 2026 22:20

Copilot started reviewing on behalf of enejb January 15, 2026 22:21 View session

Copilot AI reviewed Jan 15, 2026

View reviewed changes

simison reviewed Jan 16, 2026

View reviewed changes

Copilot AI review requested due to automatic review settings January 19, 2026 17:22

Copilot started reviewing on behalf of enejb January 19, 2026 17:23 View session

Copilot AI reviewed Jan 19, 2026

View reviewed changes

projects/packages/forms/changelog/update-jetpack-form-editor-add-categories Outdated Show resolved Hide resolved

Copilot AI review requested due to automatic review settings January 19, 2026 21:53

Copilot started reviewing on behalf of enejb January 19, 2026 21:53 View session

edanzer reviewed Jan 20, 2026

View reviewed changes

edanzer previously approved these changes Jan 20, 2026

View reviewed changes

enejb and others added 13 commits January 20, 2026 11:35

add changelog

b8c01d2

Add tests for category-utils functions

908c680

Introduces unit tests for registerFormCategories and unregisterFormCategories to verify correct category insertion, removal, immutability, and reversibility.

update text to input

ee438e4

Co-authored-by: Copilot <[email protected]>

Add getFormCategorySlug test

72f8b4a

Update categories

1554021

Category assignments: - Basic: Text, Textarea, Number, Date, Time - Contact info: Name, Email, Phone number, Website - Choice: Checkbox, Dropdown, Single choice, Multiple choice, Image select - Advanced: File upload, Slider, Rating, Hidden, Terms Consent

update the changelog

b7db60e

Convert to pass ts linter

1f610c9

Update the return of setupFormEditorCategories

54072db

fix test

bacabc0

Add core/button block

02a169e

Move time and date field to advanced

d5401e3

enejb dismissed edanzer’s stale review via d5401e3 January 20, 2026 19:43

enejb force-pushed the update/jetpack-form-editor-add-categories branch from 4c2695f to d5401e3 Compare January 20, 2026 19:43

Add multistep form category

395ebbf

Copilot AI review requested due to automatic review settings January 20, 2026 20:10

Copilot started reviewing on behalf of enejb January 20, 2026 20:10 View session

Update tests

077dc15

Copilot AI reviewed Jan 20, 2026

View reviewed changes

projects/packages/forms/changelog/update-jetpack-form-editor-add-categories Outdated Show resolved Hide resolved

Copilot AI reviewed Jan 20, 2026

View reviewed changes

enejb added 2 commits January 20, 2026 13:35

Do not use the settings object

ab43d37

fix linter

61a960f

Copilot AI review requested due to automatic review settings January 21, 2026 12:49

Copilot started reviewing on behalf of enejb January 21, 2026 12:50 View session

enejb added 2 commits January 21, 2026 04:52

update changelog

10bba56

prefix categories with jetpack

8b09478

Copilot AI reviewed Jan 21, 2026

View reviewed changes

	* This reads the category from supports.jetpack_form.category and maps
	* This reads the category from each child block's `form_editor.category` field and maps

	* Blocks define their category in supports.jetpack_form.category using the short name
	* Blocks define their category in form_editor.category using the short name

Forms: Add granular block categories to form editor #46626

Are you sure you want to change the base?

Forms: Add granular block categories to form editor #46626

Uh oh!

Conversation

enejb commented Jan 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Proposed changes:

Block categorization:

Other information:

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Testing instructions:

Uh oh!

github-actions bot commented Jan 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Jan 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

jp-launch-control bot commented Jan 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Coverage Summary

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Copilot AI Jan 15, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Copilot AI Jan 15, 2026

Choose a reason for hiding this comment

Uh oh!

ilonagl commented Jan 16, 2026

Uh oh!

simison commented Jan 16, 2026

Uh oh!

ilonagl commented Jan 16, 2026

Uh oh!

simison commented Jan 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

simison Jan 16, 2026

Choose a reason for hiding this comment

Uh oh!

enejb Jan 19, 2026

Choose a reason for hiding this comment

Uh oh!

simison Jan 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

simison Jan 16, 2026

Choose a reason for hiding this comment

Uh oh!

enejb Jan 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

enejb commented Jan 15, 2026 •

edited

Loading

github-actions bot commented Jan 15, 2026 •

edited

Loading

github-actions bot commented Jan 15, 2026 •

edited

Loading

jp-launch-control bot commented Jan 15, 2026 •

edited

Loading

simison commented Jan 16, 2026 •

edited

Loading

simison Jan 20, 2026 •

edited

Loading

enejb Jan 19, 2026 •

edited

Loading

edanzer left a comment •

edited

Loading