composer-patches
composer-patches copied to clipboard
Defined base structure and all options available README
For people new to this is important to know what options are available and what are the benefits of using them, for example did not knew that prefer install to source will allow to use git apply instead of patch which was one of the reasons a patch was applied but still flagged as not applied (did not look further into this to understand why).
"config": {
"preferred-install": "source"
},
Agreed - i did not know that either.
I've made a note to document this in main
.
Can you take a look at https://docs-staging.cweagans.net/composer-patches/usage/configuration/ and let me know if it's along the lines of what you were looking for?
(The configuration options there are specific to 2.x)
@cweagans documentation looks good, what about "preferred-install": "source"
which was defining via what software a patch was applied, i.e. either using patch
or git
(see body of the issue), currently i do not see this configuration and was wondering if the logic changed maybe since this issue has been raised?
It has changed. Right now, main only uses git to apply patches. If the target isn't a git repo, the plugin creates a temporary git repo so that the patch can be applied.