- 🇺🇸United States Webbeh Georgia, USA
Why did you create two patches from the MR?
- 🇮🇳India praveenpb Bangalore
@Webbeh, I thought to update the patch file name so uploaded a second one but I already removed the first one from display.
- 🇧🇬Bulgaria pfrenssen Sofia
@praveenpb FYI it's not needed to manually create patches from the MR, you can directly link to the auto-generated patch: https://git.drupalcode.org/project/fakeobjects/-/merge_requests/1.diff - see the "plain diff" link in the MR section above.
- 🇮🇳India praveenpb Bangalore
@pfrenssen, The problem of using auto-generated patch is that it changes whenever someone pushed something to the MR, and it will be applied to our project when we run composer install/update without our knowledge. If someone pushes a buggy code it is not safe to use it, but if you create a patch manually, it will not change that patch.
- 🇧🇬Bulgaria pfrenssen Sofia
@praveenpb fair enough, but you can just commit it locally in your project if you want to pin a specific version of a MR, or use the branch from the issue fork directly and pin the commit in composer.json.