Cameron Eagans

If `composer install` determines that there are no packages to install, it's likely that nothing would happen (since patches are applied after installation of each package). In theory, if the...

2 and 3 are already implemented, I think. 1 seems like a good idea as an opt-in behavior. I probably won't get to it in the near future -- should...

I need to know a _lot_ more about your environment. Sorry I didn't specify, but can you provide all of the information requested by the reproducible bug issue form? https://github.com/cweagans/composer-patches/issues/new?assignees=&labels=bug&projects=&template=bug.yml...

Please provide _all_ of the information from that template. Contents of composer.json and contents of patches.lock.json are important.

The `composer -vvv` output says that a different patch failed: ``` 'git' -C 'html/core' apply --check --verbose -p2 '/home/j/.cache/composer/patches/8aece04cd33ab44a512227d6191ba67c47106af6ede2efdb80f84dbf46c509d6.patch' Executing command (CWD): 'git' -C 'html/core' apply --check --verbose -p2 '/home/j/.cache/composer/patches/8aece04cd33ab44a512227d6191ba67c47106af6ede2efdb80f84dbf46c509d6.patch'...

> Suggested process: keep your git apply default but do a dry-run first (assuming git apply does dry-runs) then if the dry-run is successful use git apply, if not, try...

> Hi cweagans, please do not take this personally, I have a high respect for your work and appreciate your efforts. I could perhaps sponsor your work if there's a...

I won't say no :) I'll update here if I beat you to it!

Presently, yes, that's expected. I'd be open to a PR that makes composer status report things in a patch-aware way!

This is not ready to be merged (no docs, no tests) + I haven't had time to work on it. No real timeframe!