Cameron Eagans

Not sure what was going on here. `main` is a lot different now though.

Looks like a bad patch. Also, `main` doesn't resolve patches from dependencies anymore.

I've made a note to consider this for 2.x. I'm not 100% sold on this though -- it might be better to just unconditionally define the patches, and then if...

In `main`, there is now a patches.lock file and patches are cached in the composer cache. The likelihood of this happening if you've tested your patch locally is very low.

I've made a note to include this in #447.

2.x doesn't have the concept of patches resolved from dependencies, so ignoring patches won't be as big of a thing. #447 if you're curious. All patches are defined in the...

> Got the same behavior. Is the "preferred-install": "source" a mandatory option? Not mandatory, but significantly increases the chances that a patch will apply. Closing this -- `main` works a...

I've made a note to capture this in #447.

Probably not going to do this, sorry.

`main` now gives you a ton of flexibility with which patchers are enabled. If you don't want the git patcher, you can simply disable it. You can also define your...