Let me first preface this by saying that, as documented here, you should not put a gitlab MR patch link directly into your compose.json file. Instead you should download the patch file, and inlude it locally. Otherwise the patch is likely to change our from under you when the MR gets rebased onto another branch.
Unfortunately I didn't know that, and after fixing an urgent bug, our CI stopped building. It was late at night, and not a great time to be fixing the issue, so that added a layer of stress to it, as evidenced by a few panicked comments on the merge request. Still in the end, I got the patch recreated. In case you made the same mistake I did; here are the steps I took to recreate the patch:
git fetch origin <commit sha>
git checkout <commit sha>
git diff <name of tag representing your currently installed version> > <patch-file-name>.patch
diff --git <filename info>
to the line before the next diff --git <filename info>
for each file not listed in the changes tab on gitlab."fix css import getting messed up by the aggregator https://www.drupal.org/project/drupal/issues/2936067": "patches/css-import-fix.as_of_210930.patch"
Add new comment