Skip to content
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

Closed
Ig0r-M-magic42 opened this issue Aug 29, 2019 · 6 comments
Closed

Defined base structure and all options available README #281

Ig0r-M-magic42 opened this issue Aug 29, 2019 · 6 comments

Comments

@Ig0r-M-magic42
Copy link

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"
  },
@weitzman
Copy link

Agreed - i did not know that either.

@cweagans
Copy link
Owner

cweagans commented Feb 7, 2023

I've made a note to document this in main.

@cweagans cweagans closed this as completed Feb 7, 2023
@cweagans cweagans mentioned this issue Feb 7, 2023
31 tasks
@cweagans
Copy link
Owner

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?

@cweagans
Copy link
Owner

(The configuration options there are specific to 2.x)

@Ig0r-M-magic42
Copy link
Author

@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?

@cweagans
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants