Problem/Motivation

We may be able to save time on the apply phase, because we have a validator that ensures we don't have modifications to core. So as long as we can validate that, we can skip copying core back from the stage.

Proposed resolution

Exclude core on the copy-back (apply phase).

@todo: ensure our core validator is present and working first!

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

chrisfromredfin created an issue. See original summary.

phenaproxima made their first commit to this issue’s fork.

tim.plunkett made their first commit to this issue’s fork.

chrisfromredfin’s picture

Status: Active » Needs work

Test failed with "sudo: command not found" ?!

Also, does this need a test? And if so, how could we test it. AFTER the validator runs, we could change a file in /core in stage and make sure after the copy back it's not there??