Skip to content

Build: Copy Icons manifest file from Gutenberg#10795

Draft
mcsf wants to merge 4 commits intoWordPress:trunkfrom
mcsf:add/icons-manifest
Draft

Build: Copy Icons manifest file from Gutenberg#10795
mcsf wants to merge 4 commits intoWordPress:trunkfrom
mcsf:add/icons-manifest

Conversation

@mcsf
Copy link
Contributor

@mcsf mcsf commented Jan 26, 2026

Companion PR to Gutenberg's WordPress/gutenberg#74943

See the original PR for more context. This change will ensure that Gutenberg's packages/icons/src/manifest.php will be available in Core at wp-includes/icons/manifest.php along with the core SVG files at wp-includes/icons/library/*.svg.

Trac ticket:


This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

@github-actions
Copy link

Hi @mcsf! 👋

Thank you for your contribution to WordPress! 💖

It looks like this is your first pull request to wordpress-develop. Here are a few things to be aware of that may help you out!

No one monitors this repository for new pull requests. Pull requests must be attached to a Trac ticket to be considered for inclusion in WordPress Core. To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description.

Pull requests are never merged on GitHub. The WordPress codebase continues to be managed through the SVN repository that this GitHub repository mirrors. Please feel free to open pull requests to work on any contribution you are making.

More information about how GitHub pull requests can be used to contribute to WordPress can be found in the Core Handbook.

Please include automated tests. Including tests in your pull request is one way to help your patch be considered faster. To learn about WordPress' test suites, visit the Automated Testing page in the handbook.

If you have not had a chance, please review the Contribute with Code page in the WordPress Core Handbook.

The Developer Hub also documents the various coding standards that are followed:

Thank you,
The WordPress Project

const dest = path.join( wpIncludesDir, fileMap.destination );
fs.mkdirSync( dest, { recursive: true } );
for ( const src of fileMap.files ) {
const matches = fs.globSync( path.join( gutenbergDir, src ) );
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note to self: trunk's stated Node version is 20, glob was added in 22.

@mcsf mcsf force-pushed the add/icons-manifest branch from 89b9ed9 to 424cee9 Compare February 12, 2026 11:45
@github-actions
Copy link

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@t-hamano
Copy link
Contributor

Since #10909 includes the icon copy process, do we close this PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants