Patch drupal.org project (core/module/theme) with issue fork The new fork based merge request (MR) approach is pretty neat to get the patches created/reviewed/merged. However, if you are using the patch via cweagans/composer-patches, we have a few options.
Option 1: we can use the MR  to add the patch like this:
&quot;drupal/message&quot;: {
  &quot;3186091&quot;: &quot;https://git.drupalcode.org/project/message/-/merge_requests/1.patch&quot;
}

but it means any new change pushed to the fork/branch, would get automatically added. As the patch file gets pulled on composer install.
Option 2:
We could use the fork's branch and commit hash to keep the patch static, but once the MR merged, the fork might get deleted and breaks the build.
Option 3: Obviously we can generate the patch from the MR and upload to the issue comment, but it seems a duplicate effort and hard to keep up with an active core issue (right now, we just need to update the patch file in composer.json or composer.patches.json)
Is there a way to have the current patch file behavior in the new fork based issue queue?
UPDATE: Both option 1 and (probably) option 3 are documented on drupal.org
It has been discussed already in the Opt-in to the Drupal.org Issue Forks and Merge Requests beta thread, see 3152637#comment-13820062.  As of now there is no straight way to integrate commits in composer patch work flow. You need to download the patch file manually by appending .patch to the merge request URL and copy it locally into your project to get it applied in the build process.
&quot;patches&quot;: {
    &quot;drupal/foobar&quot;: {
        &quot;3200808 - Lorem ipsum&quot;: &quot;./patches/3200808-3.patch&quot;
    }
}

You can get additional information on how to generate patch from the commit Id from the guide: Patch files for use with Composer.