3 Improving the text
source | link

ToTraditional

You can use the traditional method:

git apply MAGEPatch-20181106.patch

or

patch -p1 < MDVA-14172_EE_2.2.6_COMPOSER_v1.patch    

Composer

Or to solve the same situation with files being patched in the vendor directory, there is a good article on it here: http://jamescowie.me/blog/2016/12/Composer-Magento-Patches/

We did something similar in our composer file:

...
   "extra": {
        "magento-force": "override",
        "composer-exit-on-patch-failure": true,
        "patches": {
            "magento/module-cache-invalidate": {
                "GH 8815: Varnish purge requests can overrun size limit": "patches/composer/github-issue-8815.patch"
            },
        }
    }
...

In our Magento root, we have a patches/composer directory which is where we reference them and in the extras/patches section, we tell it which Magento module to patch.

Ironically I found this post when looking at how this was done only to find our solution was already in place by our initial vendor.

To solve the same situation with files being patched in the vendor directory, there is a good article on it here: http://jamescowie.me/blog/2016/12/Composer-Magento-Patches/

We did something similar in our composer file:

...
   "extra": {
        "magento-force": "override",
        "composer-exit-on-patch-failure": true,
        "patches": {
            "magento/module-cache-invalidate": {
                "GH 8815: Varnish purge requests can overrun size limit": "patches/composer/github-issue-8815.patch"
            },
        }
    }
...

In our Magento root, we have a patches/composer directory which is where we reference them and in the extras/patches section, we tell it which Magento module to patch.

Ironically I found this post when looking at how this was done only to find our solution was already in place by our initial vendor.

Traditional

You can use the traditional method:

git apply MAGEPatch-20181106.patch

or

patch -p1 < MDVA-14172_EE_2.2.6_COMPOSER_v1.patch    

Composer

Or to solve the same situation with files being patched in the vendor directory, there is a good article on it here: http://jamescowie.me/blog/2016/12/Composer-Magento-Patches/

We did something similar in our composer file:

...
   "extra": {
        "magento-force": "override",
        "composer-exit-on-patch-failure": true,
        "patches": {
            "magento/module-cache-invalidate": {
                "GH 8815: Varnish purge requests can overrun size limit": "patches/composer/github-issue-8815.patch"
            },
        }
    }
...

In our Magento root, we have a patches/composer directory which is where we reference them and in the extras/patches section, we tell it which Magento module to patch.

Ironically I found this post when looking at how this was done only to find our solution was already in place by our initial vendor.

2 added 37 characters in body
source | link

To solve the same situation with files being patched in the vendor directory, there is a good article on it here: http://jamescowie.me/blog/2016/12/Composer-Magento-Patches/

We did something similar in our composer file:

...
   "extra": {
        "magento-force": "override",
        "composer-exit-on-patch-failure": true,
        "patches": {
            "magento/module-cache-invalidate": {
                "GH 8815: Varnish purge requests can overrun size limit": "patches/composer/github-issue-8815.patch"
            },
        }
    }
...

In our magentoMagento root, we have a patches/composer directory which is where we reference them and in the extras/patches section, we tell it which magentoMagento module to patch.

Ironically I found this post when looking at how this was done only to find our solution was already in place by our initial vendor.

To solve the same situation with files being patched in the vendor directory, there is a good article on it here: http://jamescowie.me/blog/2016/12/Composer-Magento-Patches/

We did something similar in our composer file:

...
   "extra": {
        "magento-force": "override",
        "composer-exit-on-patch-failure": true,
        "patches": {
            "magento/module-cache-invalidate": {
                "GH 8815: Varnish purge requests can overrun size limit": "patches/composer/github-issue-8815.patch"
            },
        }
    }
...

In our magento root, we have a patches/composer directory which is where we reference them and in the extras/patches section we tell it which magento module to patch.

Ironically I found this post when looking at how this was done only to find our solution was already in place by our initial vendor.

To solve the same situation with files being patched in the vendor directory, there is a good article on it here: http://jamescowie.me/blog/2016/12/Composer-Magento-Patches/

We did something similar in our composer file:

...
   "extra": {
        "magento-force": "override",
        "composer-exit-on-patch-failure": true,
        "patches": {
            "magento/module-cache-invalidate": {
                "GH 8815: Varnish purge requests can overrun size limit": "patches/composer/github-issue-8815.patch"
            },
        }
    }
...

In our Magento root, we have a patches/composer directory which is where we reference them and in the extras/patches section, we tell it which Magento module to patch.

Ironically I found this post when looking at how this was done only to find our solution was already in place by our initial vendor.

1
source | link

To solve the same situation with files being patched in the vendor directory, there is a good article on it here: http://jamescowie.me/blog/2016/12/Composer-Magento-Patches/

We did something similar in our composer file:

...
   "extra": {
        "magento-force": "override",
        "composer-exit-on-patch-failure": true,
        "patches": {
            "magento/module-cache-invalidate": {
                "GH 8815: Varnish purge requests can overrun size limit": "patches/composer/github-issue-8815.patch"
            },
        }
    }
...

In our magento root, we have a patches/composer directory which is where we reference them and in the extras/patches section we tell it which magento module to patch.

Ironically I found this post when looking at how this was done only to find our solution was already in place by our initial vendor.