Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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!
Issue fork project_browser-3365345
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:
Comments
Comment #5
chrisfromredfinTest 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??