-
-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Defined base structure and all options available README #281
Comments
Agreed - i did not know that either. |
I've made a note to document this in |
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 |
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. |
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).
The text was updated successfully, but these errors were encountered: