[wp-trac] [WordPress Trac] #56179: Tools: Automate backporting core blocks from Gutenberg to Core

[WordPress Trac]

#56179: Tools: Automate backporting core blocks from Gutenberg to Core
--------------------------------------+-----------------------
 Reporter:  gziolo                    |       Owner:  gziolo
     Type:  task (blessed)            |      Status:  reopened
 Priority:  normal                    |   Milestone:  6.1
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-----------------------

Comment (by gziolo):

 > Also, these files are supposed to be overwritten every time WP is build,
 right? So why commit the potentially old versions of them :)

 Thank you for raising the issue. It's a different use case though because
 the script that updates 3 newly extracted files is totally optional. We
 might want to reword the code comment that gets included in the file after
 it gets recreated when core blocks change in a specific way in the
 Gutenberg plugin - new block added,  a block promoted from an experiment
 to a stable version, block transitioned from static to dynamic or the
 other way around:

 https://core.trac.wordpress.org/browser/trunk/tools/release/sync-stable-
 blocks.js?rev=53688#L22

 > // This file was autogenerated by tools/release/sync-stable-blocks.js,
 do not change manually!

 To further clarify, `tools/release/sync-stable-blocks.js` doesn't run on
 every build. It gets only triggered when calling `npm run sync-gutenberg-
 packages` that you run only when bringing new changes from the Gutenberg
 plugin to WordPress core. I expect those files to change at most a few
 times for a given major WordPress release.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/56179#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform