[wp-trac] [WordPress Trac] #64393: Change how we include Gutenberg in Core

[WordPress Trac]

#64393: Change how we include Gutenberg in Core
------------------------------+--------------------------
 Reporter:  youknowriad       |       Owner:  youknowriad
     Type:  task (blessed)    |      Status:  reopened
 Priority:  high              |   Milestone:  7.0
Component:  Build/Test Tools  |     Version:
 Severity:  blocker           |  Resolution:
 Keywords:  has-patch         |     Focuses:
------------------------------+--------------------------

Comment (by dmsnell):

 Some of my normal scripts which run on a fresh checkout of `wordpress-
 develop` no longer work, because the PHP files are missing without the
 build step.

 This particularly affects my benchmarking scripts, which is what led me to
 this now (I did not set out looking to find problems with it). My
 benchmarking of WordPress releases and HTML API and other performance-
 related changes involves running tests for hours, as it is, flipping
 between fresh database and code states.

 With the addition of the build step this is multiplying my required test
 runtimes into //days// and more.

 This is all due to the PHP files which were removed from the repository
 and then added to `.gitignore`. Could we leave the PHP files intact so
 that Core isn’t missing necessary classes on a checkout? And then when we
 pull in the code from Gutenberg, allow for those “backports” to also
 update the version-controlled files? Surely we could detect if there were
 changes in Core that weren’t in Gutenberg with something like `git diff
 PREV_REF...CURRENT_REF -- src/wp-includes/class-wp-block-parser.php` as a
 way to avoid overwriting changes.

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