Option 1: we can use the MR to add the patch like this:
but it means any new change pushed to the fork/branch, would get automatically added. As the patch file gets pulled on
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
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