Store Drupal patches as part of the platform's code base.
We presently retrieve patches to Drupal packages by referencing the patch's URL in composer.json and downloading it as part of running composer install.
Also note that if more commits are added to the merge request, the patch that you can download from that URL will change. You must, download the patch file and save it locally.
Description of what is to be accomplished.
Download each of the patches referenced in composer.json.
Place the patch file in the patches directory, with a sub-directory structure matching the package name. e.g. Patches for drupal/core belong in patches/drupal/core and patches for drupal/paragraphs belong in patches/drupal/paragraphs.
Add the patch's download URL to the "key" (e.g. "3094343 : Garbled purge tag IDs (https://www.drupal.org/files/issues/2023-09-07/purge-3094343-15.patch)")
Give the patch a filename matching its Drupal.org issue ID. (For the preceding example, that would be 3094343.patch)
Store Drupal patches as part of the platform's code base.
We presently retrieve patches to Drupal packages by referencing the patch's URL in
composer.jsonand downloading it as part of runningcomposer install.The current guidance from Drupal.org is that patches be downloaded and stored as part of the code base.
Key advice (emphasis added)
Description of what is to be accomplished.
composer.json.patchesdirectory, with a sub-directory structure matching the package name. e.g. Patches fordrupal/corebelong inpatches/drupal/coreand patches fordrupal/paragraphsbelong inpatches/drupal/paragraphs."3094343 : Garbled purge tag IDs (https://www.drupal.org/files/issues/2023-09-07/purge-3094343-15.patch)")3094343.patch)Resources:
Prerequisites
Sub-Tasks
Notes